On-error mapping scenarios to avoid
Avoiding these common issues improves the reliability and maintainability of your orchestration flows:
Not defining an on-error path
Omitting an error handling state for an activity can cause the Ssymphony to terminate unexpectedly. Always specify fallback paths for critical activities.
Failing to update mappings after renaming or restructuring states
If a state is renamed or reorganized without updating its on-error mappings, those mappings become invalid. Always revalidate your symphony after structural changes.
Neglecting to test error scenarios
If you test only the normal paths, the orchestration is vulnerable to failures. Simulate error conditions during testing to confirm that on-error paths function correctly and do not disrupt downstream processing.
Mapping on-error paths across switch branches
Mapping an on-error path from an activity in one switch branch to an activity in a different branch creates an invalid execution path. The target branch may not execute at runtime, making the error path unreachable. Always keep on-error mappings within the same branch, or route them to activities outside the switch construct.
Mapping on-error paths from outside a switch to inside a switch branch
Configuring an on-error path from an activity that executes before a switch construct to an activity inside a switch branch is not allowed. The target activity is conditionally executed and may not be reachable during error handling.