# Troubleshoot automations

> Diagnose validation issues, missing runs, inactive automations, and failed steps using the builder and Activity execution details.

URL: https://www.agencytitan.com/help/automations/troubleshoot-automations/

Start with what AgencyTitan shows in the builder or **Activity**. Builder issues explain why a draft cannot publish. Execution details show where an accepted run stopped and the error surfaced by that step. Open the automation from **Settings**, then **Automations** ([/settings/automations](https://app.agencytitan.com/settings/automations)).

## A draft cannot publish

1. Open **Builder**.
2. Select the numbered issue control in the toolbar.
3. Open each affected node.
4. Complete the settings under **Configuration Errors**.
5. Confirm the graph has at least one trigger and a connected path.
6. Save each node, then select **Save Draft**.
7. Reload and confirm the issue count is clear before publishing.

The publish control's tooltip also summarizes why publishing is blocked.

## An automation did not start

Check these visible states first:

1. Confirm the automation is **Published** and **Active**.
2. Confirm you are viewing the correct automation and date range in **Activity**.
3. Review the trigger configuration and any conditions.
4. For a schedule, verify schedule type, timezone, and **Next Scheduled Executions**.
5. For a button or link, confirm the correct source is connected to that automation.
6. For an integration event, confirm the required integration is available to the agency.

If the header says **Draft (v# is Active)**, the active version is receiving triggers rather than the draft you are viewing.

## A run failed

1. Open **Activity** and select the **Failed** row.
2. Read the execution timeline from the trigger to the red failed step.
3. Expand the failed step when more detail is available.
4. Read the **Error** message.
5. Use **Tree** or **Raw** when the summarized message is not enough.
6. Copy the execution ID when sharing the failure through [Submit a ticket](/help/submit-a-ticket/).
7. Fix the draft, publish it, and use **Re-run** only when repeating earlier actions is safe.

![Failed execution showing a button trigger, a blocked request step, the Automation failed event, and an outbound host error](/docs/screenshots/automations-v1/failed-run-details.png)

In the example above, the HTTP action used a blocked local address. Activity shows **Failed**, identifies the failing action in the timeline, and surfaces **Outbound URL host is not allowed**. Your error text will reflect the step that failed.

## Common symptoms

| Symptom | What the UI can tell you | What to do |
| --- | --- | --- |
| Publish control is disabled | Issue count and tooltip identify validation problems | Open every issue, complete required fields, connect the path, and save the draft |
| Published automation has no runs | Header may show **Inactive** | Turn on the toggle and confirm **Active** |
| Draft changes are not running | Header shows **Draft (v# is Active)** | Publish the draft when ready; until then the named version remains active |
| Expected run is missing from Activity | Date filter excludes it or the trigger did not start | Expand the date range, refresh, then review trigger and condition settings |
| Condition is missing after reopening a trigger | It did not persist in the draft | Add it again, select **Done**, save the node and draft, and [submit a ticket](/help/submit-a-ticket/) if it repeats |
| Row shows **Failed** | One or more steps surfaced an error | Open the row and inspect the red step and error details |
| Row shows **Running** or **Waiting** | The run is not terminal | Refresh before re-running or changing the automation |
| Re-run could duplicate work | Earlier actions may have succeeded before a later failure | Review the timeline and side effects; repair manually or re-run only when safe |
| Automation should stop taking new work | It is active | Turn it inactive; existing activity remains visible |

## When submitting a ticket

Include the automation name, execution ID, start time, trigger, failed step, and surfaced error. Use **Copy URL** and **Copy ID** from execution detail instead of copying a long raw stack. See [Submit a ticket](/help/submit-a-ticket/).

## Related articles

- [Create an automation](https://www.agencytitan.com/help/automations/create-an-automation/): Create an automation draft, choose from the triggers available in the builder, and add field or related-record conditions.
- [Add actions and steps](https://www.agencytitan.com/help/automations/add-actions-and-steps/): Add and configure actions, connect nodes in execution order, and use control-flow and utility steps in the automation builder.
- [Publish and manage automations](https://www.agencytitan.com/help/automations/publish-and-manage/): Publish and activate an automation, edit a live version safely, restore an older version as a draft, duplicate, organize, or delete.
- [View automation run history](https://www.agencytitan.com/help/automations/view-run-history/): Use the Activity tab to filter automation runs, open an execution timeline, inspect step errors, copy identifiers, and re-run safely.