Introduction
If a Centerprise workflow starts failing after a JSON or XML source changes, the issue is often caused by a mismatch between the incoming file structure and the schema configured in the project. Even when the file is still valid, added, removed, renamed, or reordered fields can break parsing and mapping.
Issue description
This troubleshooting guide helps you resolve workflow failures that occur when Centerprise reads JSON or XML files whose structure has changed since the project was configured. Common causes include schema drift, changed nesting, missing optional elements, repeated nodes, or data type changes in the source file.
Signs
- The workflow fails during source reading, parsing, or mapping.
- Fields that previously populated correctly now appear blank or missing.
- The source file opens successfully outside Centerprise but fails in the workflow.
- Errors appear after a system upgrade, configuration change, or file format update in the source system.
Basic troubleshooting steps
Use the following checklist to identify the most common causes of JSON or XML parsing failures.
- Confirm that the incoming file still matches the schema configured in the project.
- Check whether element names, attribute names, or field names have changed.
- Verify nesting levels and repeating nodes to ensure the structure is still consistent.
- Review data types for fields that may now contain different values, such as text instead of numbers or dates.
- Check whether optional elements are now missing or appearing more than once.
- If the file comes from another system, confirm whether that system changed after an upgrade or configuration update.
Advanced troubleshooting steps
Step 1: Refresh the source definition
Open the Centerprise project and refresh or re-import the JSON or XML source definition so it reflects the current file structure. This helps Centerprise recognize new fields, removed fields, and updated nesting.
Step 2: Remap changed fields
Review the source-to-target mappings and update any fields that were renamed, moved, or removed. If a field is no longer available, replace it with the correct current field or apply a placeholder value where appropriate.
Step 3: Validate optional and repeating elements
Confirm whether optional elements are now missing and whether repeating nodes are being returned differently than before. Adjust the workflow logic to handle absent values, repeated records, or changed hierarchy as needed.
Step 4: Test with a sample file
Run the workflow again using a current sample file from the source system. Compare the results with the expected output to confirm that the structure is aligned and the mappings are correct.
Step 5: Review run history and server logs
If the workflow still fails, review the run history and server logs for parsing errors, missing node references, or type conversion issues. These details can help identify the exact point where the structure no longer matches the project configuration.
Diagnostic tools and resources
- Centerprise run history
- Centerprise server logs
- Current sample JSON or XML file from the source system
- Project source definition or schema file
Contact support
If you still cannot resolve the issue, contact Astera Support with the following details:
- The Centerprise version you are using
- A sample of the updated JSON or XML file
- The source definition or schema used in the project
- The exact error message from the run history or server logs
- A description of any recent changes in the source system
Additional resources
For more help with Centerprise workflows, review the latest documentation, release notes, and known issues in the Astera Support center. If the source system changed after an upgrade, also check whether a schema or output format update is required on the producing system.
Conclusion
When JSON or XML files change structure, Centerprise workflows may fail until the source definition and mappings are updated to match the new format. Refresh the schema, remap changed fields, validate optional and repeating elements, and review logs if the issue continues. Once the workflow is aligned with the current file structure, rerun it with a sample file to confirm the fix.
Disclaimer
This guide is intended for troubleshooting purposes only. Your specific steps may vary depending on your Centerprise version, project design, and source system behavior. Use your discretion when applying changes and contact support if you need assistance.
0 Comments