Campaign: No workflow failure notification when a workflow hangs
In some Adobe Campaign workflow scenarios, a workflow can remain in a running, pending start, or repeatedly auto-resumed state instead of moving to a clear failed state. When this happens, standard workflow failure notifications may not be triggered, which can delay detection and remediation.
Description description
A workflow was observed entering a hanging state after a schema-level configuration error was introduced. Instead of failing definitively and sending a workflow failure alert, the workflow stayed in an intermediate processing state and was automatically resumed by the system.
Typical symptoms included:
- The workflow remained in a running or pending state for an extended period.
- Automatic resume or restart events appeared in the logs.
- Schema parsing or execution-context initialization errors were present.
- No workflow failure notification was sent to the configured supervisors or operators.
This behavior is important because workflow error-management settings are designed to react to workflows that fail. In this scenario, the workflow did not always transition into a failed status, so the notification logic was not triggered.
Resolution resolution
At this time, no product fix is available for this scenario because the exact scenario could not be reproduced consistently outside the original environment and the triggering condition was tied to an invalid human configuration input.
Recommended guidance:
- Validate schema changes carefully before promoting them.
- Check for invalid field references, typographical mistakes, or inconsistent schema definitions if workflows appear to hang without failing.
- Do not rely solely on standard failure notifications to detect this class of issue.
- Add operational monitoring for workflows that remain in running, pending, or repeatedly resumed states longer than expected.