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. |
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.
Filtering Runs
Use the filters at the top of the table to narrow down what you’re looking at.Reference or ID
Search by the record reference (e.g. a deal name or record ID from your source app) or by Fourgent’s internal run ID.
Date
Filter runs by a specific date or date range. Useful when investigating an incident or checking activity from a particular time window.
Status
Filter by outcome — Failed, Finished, Running, Pending, or Skipped. Use Failed to quickly surface all runs that need attention.
Workflow
Filter by a specific integration. If you have multiple workflows running, this lets you focus on one at a time.
Row Actions
Each run row has three actions on the right side.Comment
Add a note to a run — useful for flagging known issues or leaving context for your team.
View Details
Opens the full run log — the trigger payload, each step that executed, any error messages, and the final result.
More Options
Additional actions including re-triggering the run with its original payload.
Investigating a Failed Run
If a run shows Failed, here’s how to find out what went wrong: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.
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.
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.
Related
Overview
See aggregated run counts and trends across your whole workspace.
Connections
Reconnect or update app credentials if a failed run points to an auth issue.
Workflows
View and manage the integrations that are generating these runs.
How It Works
Understand what happens during a run and how the Fourgent Engine handles retries and failures.