> ## Documentation Index
> Fetch the complete documentation index at: https://80x.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Troubleshooting a failing Attio workflow starts in the run viewer, not in the block editor.

Troubleshooting a failing Attio workflow starts in the run viewer, not in the block editor. The run viewer is the screen that shows each run step by step. For every block, it shows the inputs the block received and the outputs it produced. Read it from the top down to find where the first wrong value entered the chain. Open it before you change any configuration. Most "broken" workflows are wired correctly and simply fed bad data. For the run viewer, the difference between draft and published runs, and how retries work, see [Runs, debugging & publishing](/explanation/runs-and-debugging).

<CardGroup cols={2}>
  <Card title="Common errors" icon="triangle-alert" href="/troubleshooting/common-errors">
    Match a symptom to its cause and fastest fix, from a workflow that never fired to an empty variable, a list-entry mismatch, or unexpected credit usage.
  </Card>

  <Card title="Production runbook" icon="clipboard-list" href="/troubleshooting/runbook">
    Step-by-step procedures for live incidents: failed runs, runaway volume, a bad data write, an external-app outage, and the weekly review that catches them early.
  </Card>
</CardGroup>

***

*Source: [Attio Help Center: Troubleshooting workflows](https://attio.com/help/reference/automations/workflows/troubleshooting-workflows). Last reviewed against the Attio Help Center, June 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.