Retry failed tasks
See failed automations, integrations, workflows, app webhooks, network syncs and held-back events in one list, and retry or dismiss them.
Updated October 13, 2026
When something that runs on its own fails, such as a message automation, an integration or a workflow, you would normally have to look for it in several places. The Failed tasks page shows all of it in one list, so you can see what went wrong, retry it through its normal route or dismiss it.
Open the failed tasks
- Open the side menu (☰, top right) and choose Failed tasks.
- Use the buttons at the top to show one or more kinds, for example Integration (4). The number is how many failed tasks of that kind there are.
- Narrow the list with Entity type, Entity id, Integration id, Failed from and Failed until, or type in the search box.
- Click a row to open the trip, transport order, shipment or integration it is about.
The table shows the Kind, What failed, what it is About, the Error, when it Failed at and whether it was Handled.
Kinds of failed tasks
| Kind | What it is | What Retry does |
|---|---|---|
| Message automation | A message automation run that ended in an error. | Runs the automation again for the same trigger. |
| Integration | A record an integration could not process, even after its own automatic retries. | Puts the record back in the integration's queue. |
| Workflow | A workflow run that failed. | Starts a new run with the same trigger data. |
| App webhook | A webhook to an installed app that failed after all retries. | Sends the webhook again. |
| Network sync | An order forwarded through the Transportial network whose synchronization failed. Only with the transportialNetwork feature. | Synchronizes the order again. |
| On hold | Outgoing events held back while an order, shipment or trip is on hold, for example "3 events held back". Only with the orderHold feature. | Releases the hold, so the held-back events are sent. |
Retry or dismiss
- Fix the cause first, for example wrong login details of an integration or a missing e-mail address.
- Click Retry at the end of the row. To handle several tasks at once, select their rows and choose Retry from the bulk actions.
- Read the summary above the table, for example 2 retried · 1 already handled.
- Click Dismiss instead for a task that no longer needs to be done.
Retried and dismissed tasks disappear from the list. Tick Show dismissed and retried to see them again; the Handled column then shows who retried or dismissed them and when.
- already handled: someone else retried the task already, or it is waiting for its retry pause to pass.
- not allowed: you lack the permission to change this kind of task.
- cannot be retried here: the task cannot be retried from this page, for example because its workflow was removed. Dismiss it, or redo the work by hand.
- failed: the retry itself was refused. Check the error and try again later.
Retry on an On hold row releases the hold of that order, shipment or trip. Only do this when the work may continue.
Retry pause for network syncs
So that a double click does not send twice, a network sync cannot be retried again right away. Administrators set the pause in Settings > Environment > Integrations with Seconds before a network sync can be retried again (60 by default).
To see the full story of a failed integration record, open the integration and use its Objects and Logs tabs. See Monitor an integration.