The on-error mapping scenarios to avoid

On-error mapping defines how a Symphony behaves when an activity fails. Proper configuration is essential to maintain orchestration stability and prevent unexpected failures. However, critical aspects can be overlooked during design and testing.

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 Symphony 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, causing validation errors. Always revalidate your Symphony after structural changes.

Neglecting to test error scenarios

If you test only the normal paths leaves orchestration vulnerable to failures. Simulate error conditions during testing to confirm that on-error paths function correctly and do not disrupt downstream processing.