> ## Documentation Index
> Fetch the complete documentation index at: https://withforerunner.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring automations

> Review run history, read failure reasons, and get automations running again

Every automation keeps a record of each time it fired. Use it to confirm an automation is doing what you expect and to find the specific step that failed when something goes wrong.

## Reviewing run history

<Steps>
  <Step title="Open the automation">
    Select the automation from the Automations page. Its run count is on the row, so you can tell at a glance whether it has fired at all.
  </Step>

  <Step title="Open the Runs tab">
    Runs are grouped by date and show whether each execution succeeded or failed, with a timestamp.
  </Step>

  <Step title="Open a run">
    Select a run to see it step by step: which trigger fired, which actions ran, whether each one succeeded, and how long it took.
  </Step>
</Steps>

A failed run names the step that failed and gives the reason, so you can tell whether it's something you can fix yourself.

## Failure notifications

When a run fails for a reason on your side, Forerunner emails you rather than waiting for someone to open the Runs tab. Notification cadence and delivery time are set in your notification settings.

Failures caused by something on Forerunner's side alert our engineering team to investigate.

<Note>
  A failed run can't be re-run today. Correct the cause and the next matching record event runs successfully.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="An automation turned itself off">
    If a field the automation depends on was changed or removed, the automation disables itself rather than running against a field that no longer matches. The error names what to fix. Point the automation at the current field and publish it again.
  </Accordion>

  <Accordion title="A task was created with no assignee">
    If the automation's assignee has been suspended, the task is created unassigned and an indicator shows on the affected step in the builder. Assign the task by hand, then update the automation to a current user.
  </Accordion>

  <Accordion title="An email to a user field failed">
    A suspended user sitting in a record's user field isn't caught until the automation runs, so an email targeting that field fails at that point. When your account suspends staff, check any automations that email a user field they might be selected in.
  </Accordion>

  <Accordion title="An automation never fired">
    Confirm its status is Live rather than Draft or Paused, and that a record of the selected type has been created or updated since it was published. Publishing doesn't act on records that already existed.
  </Accordion>

  <Accordion title="A submitter email didn't go out">
    Submitter variables only work when the submitter has a Forerunner account. If the record type allows guest submissions, use a different recipient or require sign-in on that record type.
  </Accordion>

  <Accordion title="The failure reason isn't clear">
    Contact your Customer Success Manager with the automation name and the failed run, and Forerunner will investigate.
  </Accordion>
</AccordionGroup>