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.
ColumnWhat it shows
ReferenceThe record that triggered the run — for example, a deal name or record ID from the source system
IDFourgent’s internal run ID. Use this when reporting an issue or searching for a specific execution
WorkflowThe integration that executed — shown as Source → Destination
StatusThe outcome of the run
StartedThe date and time the run was triggered

​
Run Statuses

StatusWhat it means
FinishedThe run completed successfully. Data moved as expected.
FailedThe run encountered an error and did not complete. Click the row to see what went wrong.
RunningThe run is currently in progress.
PendingThe run is queued and waiting to execute.
SkippedThe run was triggered but not executed — a workflow condition was not met. 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

Reference or ID

Search by the record reference (e.g. a deal name or record ID) or by Fourgent’s internal run ID.

Date

Filter by a specific date or date range — useful when investigating an incident or checking a particular time window.

Status

Filter by outcome. Use Failed to quickly surface all runs that need attention.

Workflow

Filter by a specific integration. Focus on one workflow at a time.

​
Row Actions

Each run row has three actions on the right side.
ActionWhat it does
Comment
message icon		Add a note to a run — useful for flagging known issues or leaving context for your team
View Details
eye icon		Opens the full run log — the trigger, each step, any error messages, and the final result
More Options
three dots		Additional actions including re-triggering the run with its original payload

​
Investigating a Failed Run

1

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

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

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

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

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 generating these runs.

How It Works

Understand what happens during a run and how Fourgent handles retries and failures.