Skip to main content
The automation log lists every run of an automation with its status, so you can check that it works, find out why a run failed, and send failed runs again. To open it, click ⋯ at the end of the automation’s row on Workflow › Automation and choose Log. The log opens as its own page, at /workflow/automation/<id>/log, so you can also bookmark it, open it in a new tab or share its link with a colleague who has access.
Required permission:
  • View automation
Automation log
The breadcrumb shows Workflow › Automation › the automation’s name, and the title shows the name with its automation type, for example Send finished deliveries to ERP (Webhook).
  1. Back: return to the Automation list, with the filters, search and page you had before.
  2. Data retention: how long runs are kept. See Data retention.
  3. All statuses: show only Success or only Failed runs.
  4. Search by date: pick one day from the calendar to show its runs. Today and Yesterday pick those days in one click, and Clear removes the date. Only one day can be picked at a time.
  5. Search by Task ID (or Search by Data ID for automations whose event isn’t a task event): find the runs for one record, for example 6ac4f1a83adc7bd9160645a1. Order automations have no search; their Order number column shows the order each run belongs to.
  6. Repush: webhook automations only. See Repushing several webhook runs.
  7. ⋯: the actions for one run:
    • View: see the full request and response of the run.
    • Retry: send this run again.
    • Download: download the whole run as a .json file.
  8. Pages: move between pages of runs. Webhook logs show 100 runs per page; other logs show 20.
The table columns:
  • Time (UTC): when the run happened, shown relative to now (for example “16 hours ago”). Point at it to see the exact time. All times in the log are in UTC.
  • Event: the event that started the run.
  • Task ID (or Data ID, or Order number for order automations): the record that started the run: a task, data source record, routing result, location record or order, depending on the event.
  • Status: Success or Failed. For webhooks, the HTTP status code your endpoint answered with is shown too, for example Failed (500) or Success (200).
If the link points to an automation that no longer exists, the page shows Automation not found with a Back to Automation button.

Reading a run

Click ⋯ on a row and choose View:
Response
The window shows the run as formatted JSON.
  1. Response and Request: switch between what your endpoint returned and what was sent (URL, method, headers and body).
  2. Copy (Response tab only): copy the response JSON, for example to share with whoever runs the receiving system, or to paste as the Sample payload of a webhook’s Custom JSON body.
Request
  1. Copy CURL (Request tab only): copy a ready-to-run cURL command that retries this run, so you can send it again from a terminal or an API tool.
The cURL command contains your own access token. Treat it like a password: don’t share it, paste it into chats or tickets, or commit it to code.

Retrying one run

Click ⋯ on a row and choose Retry:
Retry
Retry this automation? The request will be sent again exactly as it was recorded. Click Retry to send it, or Cancel. A message confirms “Retry queued”, or “Retry failed”. The retry is processed in a queue, so it is not instant. The new run appears in the log after a moment; refresh the page to see it.

Repushing several webhook runs

Webhook automations have a checkbox on each failed run, so you can send many at once:
Repush
  1. Tick the failed runs to send again, or tick the header checkbox (Select all failed logs) to select every failed run on the page.
  2. Repush: send all selected runs again. The button shows how many are selected, for example Repush 2. Repush all selected log? asks you to confirm before anything is sent. A message then tells you how many were repushed, or how many could not be.

On a phone

Automation log on a phone
Each run is a card with its time, status, event and record.
  1. Filter: opens the filter panel with the status, date and search filters. Today and Yesterday are not shown in the date calendar on a phone.
  2. Repush: webhook automations only. Tick a failed run’s checkbox on its card, then tap Repush.
  3. ⋯: the same View, Retry and Download actions as on a computer.

Data retention

Data is stored for 30 days and will be automatically deleted. Download runs you need to keep for longer. Deleting an automation also deletes its log.