Run statuses
Each run has an icon in front of it:What a run shows
- The event that started it
- When it started and how long it took
- How many steps ran
- Click the run to see each step and the error message, if there was one
Find and fix a problem
1
Run a test
Click Test run in the top bar.
2
Open the runs
Click Runs and open the newest run.
3
Find the failed step
Look for the step with an error and read the message.
4
Fix, save, run again
Change the step’s settings, click Save, and run it again.
A test run has no real shipment or order behind it, so actions that change a shipment or an order always fail in a test. To try them, switch the automation on and let a real event start it.
Common reasons a run fails
- A required setting on a step is empty.
- A Slack or webhook address is wrong, or a connected app’s login no longer works.
- A message or check uses a detail the trigger does not have. See the list of details per trigger in Build an automation.
- The shipment is in the wrong state for the action, for example Set shipment on hold on a shipment that is already sent.