> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/troubleshooting/failed-actions.md).

# Failed Actions

**Settings → Monitoring → Failed Actions** *(beta)*

One page shows every automation action that failed during a run, across all your sequences and workflows. No more opening each automation and checking its runs one by one. Failures arrive here org-wide, newest first, so you spot problems fast and jump straight to the run that broke.

The page needs the data-management settings permission, the same one that shows the rest of the Monitoring section.

***

## What a row is

Each row is **one failed action execution**. A specific action step, in a specific run of a sequence or workflow, that ended in an error. One misconfigured automation can produce many rows, one per affected run.

| Column         | Shows                                                                          |
| -------------- | ------------------------------------------------------------------------------ |
| **When**       | The time the action failed                                                     |
| **Automation** | The sequence or workflow it belongs to. Click to open the automation           |
| **Action**     | The action type that failed, such as Send Email, Update Person or Find Records |
| **Module**     | **Sequence** or **Workflow**                                                   |
| **Error**      | The error message, truncated. Open the row for the full text                   |

Rows survive the deletion of their automation, since the failure is history. The automation link stops working at that point.

## Finding the failure you care about

* **Search** matches the automation name and the error message text.
* **Filters** narrow by module type, by one or more action types, or by a date range. The filter button carries a count of active filters, and **Clear filters** resets them.
* The list loads more as you scroll. It does not update live, so press **Refresh** for the latest failures.

## The detail view

Click a row to open the failure detail:

* **Error message**, the full text, with a copy button.
* **Summary**, holding the action type and category, the run ID, the person the run was processing, the execution duration and the row's ID.
* **Action data**, the exact input the action received as it failed, with a copy button. This is usually the fastest route to the cause, since you see the values the action was working with.
* **View automation run** jumps into the automation's run view, focused on the failed run and action. You see the failure in the context of the whole flow.

## What this page is for

Failed Actions is a diagnostic view, and it is read-only. There is no retry and no dismiss. The fix always lives in the automation itself: correct the configuration, add a fallback, repair the data. Future runs then succeed.

To watch one automation's health over time, see [Monitoring Runs & Participants](/docs/automations/monitoring-runs-and-participants.md).

Keep the distinction from the **Monitors (Failed Events)** page next door in the menu. Failed Events are ingestion messages that could not be processed on the way in. Failed Actions are automation steps that errored during a run. For the ingestion side, see [What happens when an event fails](/docs/troubleshooting/when-an-event-fails.md).

Flapjax keeps failure history for roughly 13 months by default, then ages it out.