Execution history: what happened, and what to do after an error

On the automation's detail page, the Execution History table lists every run: its status, what started it, when and how long it ran, and what went wrong. After fixing the problem, you can restart a failed run with the Run again button.

Open the automation from the Logistics → Flows list. The Execution History table shows for every run:

• Status – Running, Completed or Failed,
• Trigger – which item started it (for example, a purchase order's ID),
• Started and Duration,
• Error – if the run got stuck.

Click a row to expand the details: Action Results show step by step what worked (for example, a project created or a notification sent) and what did not.

Common causes of errors:

• an action is not fully set up (for example, no project or recipient selected),
• the webhook address is wrong or the external system does not respond,
• the item behind the event has been removed in the meantime.

Run again: for a failed run, the expanded row shows a Run again button. The system reruns it with the same event data but with the automation's current settings – so fix the problem and save first. A rerun runs the whole process again, including steps that succeeded before, so a task that was already created, for example, may be created again.