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

# Workflow Runs

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, a 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                                      |
| **Status**    | The outcome of the run                                                                             |
| **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 workflow condition was not met. 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

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

  <Card title="Date" icon="calendar-days">
    Filter by a specific date or date range — useful when investigating an incident or checking a particular time window.
  </Card>

  <Card title="Status" icon="circle-half-stroke">
    Filter by outcome. Use **Failed** to quickly surface all runs that need attention.
  </Card>

  <Card title="Workflow" icon="diagram-project">
    Filter by a specific integration. Focus on one workflow at a time.
  </Card>
</CardGroup>

***

## Row Actions

Each run row has three actions on the right side.

| Action                                      | What it does                                                                              |
| :------------------------------------------ | :---------------------------------------------------------------------------------------- |
| **Comment**<br /><sub>message icon</sub>    | Add a note to a run — useful for flagging known issues or leaving context for your team   |
| **View Details**<br /><sub>eye icon</sub>   | Opens the full run log — the trigger, each step, any error messages, and the final result |
| **More Options**<br /><sub>three dots</sub> | Additional actions including re-triggering the run with its original payload              |

***

## Investigating a Failed Run

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

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

  <Step title="Fix the root cause">
    * **Auth error?** Go to **Connections** and re-authorize the affected app.
    * **Logic gap?** Describe the fix in the chat — Fourgent will update and redeploy the integration.
  </Step>

  <Step title="Re-trigger the run">
    Use **More Options → Re-trigger** to replay the run with its original payload. No need to wait for the trigger to fire again in your source app.
  </Step>
</Steps>

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

***

## Related

<CardGroup cols={2}>
  <Card title="Overview" icon="chart-bar" href="/overview">
    See aggregated run counts and trends across your whole workspace.
  </Card>

  <Card title="Connections" icon="plug" href="/connections">
    Reconnect or update app credentials if a failed run points to an auth issue.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/workflows">
    View and manage the integrations generating these runs.
  </Card>

  <Card title="How It Works" icon="gear" href="/how-it-works">
    Understand what happens during a run and how Fourgent handles retries and failures.
  </Card>
</CardGroup>