Skip to main content
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.

​
Run Statuses

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:
1

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.
2

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.
3

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.
4

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.
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.