> ## Documentation Index > Fetch the complete documentation index at: https://docsv4.mile.app/llms.txt > Use this file to discover all available pages before exploring further. # Automation log > See every run of an automation, read the request and response, retry failed runs and download them. 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**. Required permission: * View automation
Automation log
The log opens with the automation's name as its title. 1. **All statuses**: show only **Success** or only **Failed** runs. 2. **Search by date**: show the runs of one day. Only one date can be picked at a time. 3. **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`. 4. The table columns: * **Time (UTC)**: when the run happened, shown relative to now (for example "15 hours ago"). All times in the log are in UTC. * **Event**: the event that started the run. * **Task ID** (or **Data ID**): the record that started the run: a task, data source record, routing result or location record, 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)**. * **Action**: the three buttons below. 5. **View response** (eye icon): see the full request and response of the run. 6. **Retry** (circular arrow): send this run again. 7. **Download** (arrow icon): download the run as a `.json` file. Runs are recorded when the automation is queued. For a webhook, **SUCCESS** means the request was accepted for delivery. ## Reading a run Click the eye icon:
Response
The **Response** window shows the run as JSON: the event, whether it succeeded, the status code, the **request** that was sent (URL, method and body) and the **response** your endpoint returned, with its response time. 1. **Copy**: copy the 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](/pages/workflow/automation/actions/webhook#custom-json-body). ## Retrying one run Click the circular arrow on a row:
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". ## 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. Webhook logs show 100 runs per page; other logs show 20. 2. **Repush**: send all selected runs again. The button shows how many are selected. A message tells you how many were repushed, or how many could not be. ## 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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.