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

# Workflow Runs

> Inspect, filter, and re-trigger past executions across every workflow.

Workflow Runs is your execution log. Every time an integration fires — successfully or not — it appears here as a run. You can inspect what happened, filter by status or workflow, and re-trigger any past run directly from this page.

***

## The Runs Table

Each row represents a single execution of one of your integrations.

| Column        | What it shows                                                                                                  |
| ------------- | -------------------------------------------------------------------------------------------------------------- |
| **Reference** | The record that triggered the run — for example, the deal name or record ID from the source system             |
| **ID**        | Fourgent's internal run ID. Use this when reporting an issue or searching for a specific execution             |
| **Workflow**  | The integration that executed — shown as Source → Destination (e.g. *HubSpot Closed Won → QuickBooks Invoice*) |
| **Status**    | The outcome of the run — see statuses below                                                                    |
| **Started**   | The date and time the run was triggered                                                                        |

***

## Run Statuses

| Status       | What it means                                                                                                                |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| **Finished** | The run completed successfully. Data moved as expected.                                                                      |
| **Failed**   | The run encountered an error and did not complete. Click the row to see what went wrong.                                     |
| **Running**  | The run is currently in progress.                                                                                            |
| **Pending**  | The run is queued and waiting to execute.                                                                                    |
| **Skipped**  | The run was triggered but not executed — a condition in your workflow was not met. This is expected behaviour, not an error. |

<Note>
  A **Failed** status always includes an error message. Click the eye icon on the row to open the run detail and see exactly where it failed.
</Note>

***

## Filtering Runs

Use the filters at the top of the table to narrow down what you're looking at.

<CardGroup cols={2}>
  <Card title="Reference or ID" icon="magnifying-glass">
    Search by the record reference (e.g. a deal name or record ID from your source app) or by Fourgent's internal run ID.
  </Card>

  <Card title="Date" icon="calendar">
    Filter runs by a specific date or date range. Useful when investigating an incident or checking activity from a particular time window.
  </Card>

  <Card title="Status" icon="circle-dot">
    Filter by outcome — Failed, Finished, Running, Pending, or Skipped. Use **Failed** to quickly surface all runs that need attention.
  </Card>

  <Card title="Workflow" icon="diagram-project">
    Filter by a specific integration. If you have multiple workflows running, this lets you focus on one at a time.
  </Card>
</CardGroup>

***

## Row Actions

Each run row has three actions on the right side.

<CardGroup cols={3}>
  <Card title="Comment" icon="message">
    Add a note to a run — useful for flagging known issues or leaving context for your team.
  </Card>

  <Card title="View Details" icon="eye">
    Opens the full run log — the trigger payload, each step that executed, any error messages, and the final result.
  </Card>

  <Card title="More Options" icon="ellipsis">
    Additional actions including re-triggering the run with its original payload.
  </Card>
</CardGroup>

***

## Investigating a Failed Run

If a run shows **Failed**, here's how to find out what went wrong:

<Steps>
  <Step title="Click the eye icon on the failed run">
    This opens the run detail view. You'll see the exact step where the failure occurred and the error message returned.
  </Step>

  <Step title="Read the error message">
    Common causes include: an expired API credential, a missing required field in the source record, a downstream API being temporarily unavailable, or an edge case not handled in your workflow spec.
  </Step>

  <Step title="Fix the root cause">
    If the issue is a credential, go to **Connections** and reconnect the affected app. If it's a logic gap in your workflow, describe the fix in the chat and Fourgent will update the integration.
  </Step>

  <Step title="Re-trigger the run">
    Once the issue is resolved, use **More Options → Re-trigger** to replay the run with its original payload. You don't need to wait for the trigger event to happen again in your source app.
  </Step>
</Steps>

<Warning>
  Re-triggering a run replays it with the **original payload** from when it first fired. If the source record has since changed, the replayed run will use the old data — not the updated version.
</Warning>

***