Global Fallout
A fallout is an execution that failed and now needs an operator. Global Fallout lists every fallout in the organisation for the selected environment, across all applications, so an operator can work them without opening each application in turn. The same list, scoped to one application, is the Fallouts tab on Application details.
What Engage does with a fallout automatically, before it reaches this list, is decided by fallout definitions, retry configuration, and alert rules. See Managing fallouts.
Open it
Select Global Fallout in the sidebar. The list is scoped by the environment in the header, Development or Production, and by the date range control in the toolbar.
The list
| Column | Meaning |
|---|---|
| Timestamp | When the fallout was recorded. Sortable. |
| Status | The fallout's lifecycle status. Filterable. An Exhausted tag beside it means automatic retries have run out; the fallout can still be retried by hand. |
| Application | The application the execution belongs to |
| Workflow | The workflow that failed |
| Service | The service the failing step called |
| Step | The workflow step that failed |
| Error Code | The error code, matched against error definitions |
| Error Message | The error text |
Application and Workflow appear only on this page; the application-scoped Fallouts tab omits them. The toolbar offers Search, Refresh, the date range, and Expand to Fullscreen. An empty list reads No fallouts found for the selected period. Try adjusting the date or environment filters.
Retry several at once
Rows whose status allows a manual retry have a checkbox at the left.
- Select the rows to retry.
- Select Retry Selected (N). The count is the number of selected rows that can be retried.
- Confirm in Retry N fallout(s)? with Retry.
Engage reports Retry sent for N fallout(s) and refreshes the list.
Work one fallout
Select a row. The fallout opens with its details on the right:
| Group | Fields |
|---|---|
| Details | Service, Step, Source Channel |
| Error | Name, Code, Message |
Above them sit the two actions. Both are disabled unless the fallout is waiting for a manual decision.
Retry
- Select Retry. The Retry Fallout dialog opens.
- In Action, choose one:
| Action | What it does |
|---|---|
| Retry | Re-executes the failed step from where it left off, keeping the current state and data |
| Restart | Starts the whole workflow again from the beginning, resetting all state and data |
| Restart From Step | Restarts from a step you choose in Step Name, resetting that step and everything after it while keeping earlier successful steps |
| Retry From Workflow | Reprocesses the fallout through a published retry workflow named in the manifest. Offered only when the application's manifest defines one. |
- Select Confirm Retry. Engage reports Retry sent successfully.
A fallout whose payload needs correcting first is edited in the trace's payload panel before the retry; the panel says so where editing is allowed.
Mark as Resolved
For a fallout that should not be retried, select Mark as Resolved, enter a reason in Enter the reason, and select Confirm. Engage reports Marked as resolved and the fallout leaves the manual queue.
When it does not work
| Symptom | Cause | What to do |
|---|---|---|
| Retry and Mark as Resolved are disabled | The fallout is not in a manual state; Engage is still retrying it automatically, or it is already resolved | Wait for the automatic retries to finish, shown by the Exhausted tag, then act |
| Retry Selected is disabled with rows selected | None of the selected rows is in a manual state | Select only rows whose checkbox is enabled |
| Retry failed | The retry request was rejected | Open the trace from the application's Overview table and check the failed step, then try again |
| Failed to load retry workflows | Retry From Workflow was chosen but the manifest's retry workflows could not be loaded | Choose another action, or ask the application owner to check the manifest's Retry Workflows section in Studio |
| Failed to retry all N selected fallout(s) | The bulk retry was rejected for every row | Retry one fallout from its row to see the error |
Next steps
If the same error keeps producing fallouts, change how Engage handles it automatically: Fallout definitions for what to do, Retry configuration for how often, and Alert definitions for who hears about it.