> ## Documentation Index > Fetch the complete documentation index at: https://docs.xpressbot.org/llms.txt > Use this file to discover all available pages before exploring further. # Automation Report > See how many contacts an automation ran for, how each run ended, which step is failing, and what to do about it. ## What is this? The **Automation report** is a per-automation health check, written for the person who built the automation. It shows how many contacts the automation ran for, how those runs ended, and — when something went wrong — which step failed, in plain words, with a suggested fix. The raw technical error is always one click away. ## What can I do here? * See **Contacts reached**, **Completed**, **Failed** and **Still running** at a glance * Read **Problems to fix** — failures grouped by step and cause, biggest first, each with *What to do* * Look at one row per run in the **Contacts** tab: who it ran for, how it ended, and what to do * Follow every step in the **Steps** tab, see where contacts drop off, and open a failing step to list each failure * For automations started by a webhook, see every request received in the **Activity** tab * **Export issue** to download a failing step's details to send to support ## How to use it ### Open the report Open it either way: * On the **Automations** page, click **Open automation status** on the flow's row (see [Manage Live Flows](https://docs.xpressbot.org/workspace/automation/manage-live-flows.md)). * On [Analytics](https://docs.xpressbot.org/workspace/analytics.md) → **Automations**, click an automation. The report covers the last year when opened from an automation's row; on the Analytics page it follows the date range you picked there. ### Overview The tiles show **Contacts reached** (with the total number of runs), **Completed** (the share of runs that finished every step), **Failed** (how many contacts were affected) and **Still running** (waiting for a reply or a delay). Under **Problems to fix**, failures are grouped by step and cause. Each shows how many contacts and failed runs it affected and when it was last seen. Open one to read **What to do**, or click **Show technical error** for the exact message, or **See affected contacts**. Fixing the top item helps the most contacts. Typical causes and fixes: | Problem | What to do | | - | - | | **The step took too long** | The service the step calls didn't answer in time. Check it's online, then let the automation run again | | **Required information was missing or invalid** | Open the step in the builder and check its fields. Make sure every variable it uses has a value for these contacts | | **The account didn't allow this action** | Reconnect the channel or integration and make sure it still has the permissions the step needs. Expired logins are the most common cause | | **The automation couldn't continue to the next step** | Check the step is connected to the next one and that nothing it points to was deleted. Save and publish again | | **An outside service rejected the request** | Check the connected channel or integration is still connected and its credentials are valid | | **This step isn't set up correctly** | Open the step and complete its settings, then save and publish again | If the automation has no runs, the report says **No runs in this period** — check it is active and that its trigger matches your contacts. ### Contacts One row per run. Pick **All**, **Failed**, **Completed** or **Still running** to filter. The **Result** column says how it ended — for example *Stopped at Send Template: …*, *Waiting at Ask…*, or *Stopped before finishing*. If trigger events were received but not run (for example because the contact's phone number was missing), a notice at the top says how many, and this tab shows the reason for each. ### Steps Every step in the order contacts reach it, with **Contacts reached**, **Completed**, **Failed** and a **Health** label (**Healthy**, or how many are waiting). Click a failing step to see **Failures at** that step, and use **Export issue** to download its details. ### Activity (webhook automations) For an automation started by a [webhook](https://docs.xpressbot.org/workspace/integrations/webhooks.md) or an integration, the **Activity** tab lists every request it received — including duplicates and ones that weren't run. Filter by **All**, **Processed**, **Failed** or **Duplicate**, and open a request to see its raw data. Links jump to the webhook's page or the integration's settings. ## Troubleshooting / Technical Notes * **I don't see the Activity tab.** It only appears for automations started by a webhook or integration, and needs the automations view permission. * **The numbers differ from Analytics.** The report counts runs in the selected period; check the date range. * **A failure says only "The step failed."** Open **Show technical error** for the exact reason. If it isn't clear, **Export issue** from the Steps tab and send it to [Support](https://docs.xpressbot.org/workspace/support.md). ## Related docs * [Manage Live Flows](https://docs.xpressbot.org/workspace/automation/manage-live-flows.md) * [Analytics](https://docs.xpressbot.org/workspace/analytics.md) * [Webhooks](https://docs.xpressbot.org/workspace/integrations/webhooks.md) * [Automation Overview](https://docs.xpressbot.org/workspace/automation/overview.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.