Workflow run page

The workflow run page provides a visual, read-only view of a specific workflow execution. It renders the workflow graph with real-time status indicators on every node and edge, letting you quickly understand what happened during a run — which nodes succeeded, which failed, and why.

Closed Beta Notice

The workflow run page is part of the Workflows (Beta) feature, which is currently in closed beta with limited availability.

Navigating to the run page

You can open the run page from several places in Port:

From the notifications popover

1. Click the notifications bell icon in the top-right corner of Port's UI.
2. The Runs tab shows your recent workflow runs alongside action runs, sorted by time.
3. Click on a workflow run entry to open the run page.

From the workflow runs table

1. Navigate to the Workflows page in your portal.
2. Click on a workflow, then open its Runs tab.
3. Click on a Run ID to open the run page for that execution.

From entity pages

Workflow runs associated with an entity appear in the entity's activity feed. Click on a run to open its detail page.

Page layout

The main area renders the workflow as a visual graph. The graph shows the exact workflow version that was used for the run (not the current/latest version), so you always see the nodes and connections as they were at execution time.

The graph includes:

• Header panel — An overlay on the graph showing the workflow name, overall run status, and a See logs button.
• Node details panel — Appears when you click on an executed node (see Inspecting node details below).

Run status indicators

Node status

Each node on the graph displays a visual indicator based on its execution status:

Status	Visual indicator	Description
Success	Green indicator	Node completed successfully.
Failed	Red indicator	Node execution failed.
In progress	Loading spinner	Node is currently executing.
Not executed	Dimmed appearance	Node was not reached during this run (e.g. a condition branch that was not taken).

Edge status

Edges (connections between nodes) are highlighted in green when the source node completed successfully. For condition nodes, an edge is highlighted only if the target branch was actually visited during the run.

This makes it easy to trace the execution path through the graph at a glance.

Live updates

When viewing a run that is still in progress, the page automatically refreshes the run data every 5 seconds. You can watch nodes transition from "in progress" to "success" or "failed" in real-time. Polling stops once the run completes.

Inspecting node details

Click on any node that was executed during the run to open the node details panel. The panel slides in from the right side of the graph and shows:

Field	Description
Status	The node's execution result (success, failed, or cancelled) with a color-coded label.
Variables	The node's configured variables (JQ expressions). Click See details to view the full JSON in a read-only dialog.
Outputs	The data produced by the node during execution. Click See details to view the full JSON in a read-only dialog.
Start time	When the node started executing, shown as relative time (e.g. "5 minutes ago") with exact timestamp on hover.
End time	When the node finished executing, shown as relative time with exact timestamp on hover.
Logs	Click See details to open the node's log entries in a dialog.

Inspecting data flow

Use the Outputs dialog on each node to trace how data flowed through your workflow. Comparing the outputs of sequential nodes helps you verify that JQ expressions and variable mappings are working as expected.

Viewing logs

Full run logs

Click the See logs button in the header panel to open a dialog showing logs from all nodes in the run. The logs dialog includes:

• A search bar to filter log entries by text, with a match count indicator.
• Logs grouped by node, with each node's title as a section header.
• Individual log entries showing the log level and message.

The logs dialog is useful for getting a complete picture of the run's execution, especially when debugging failures across multiple nodes.

Log availability

The See logs button is disabled when no logs have been recorded for the run. Logs are only available for nodes whose backends report them — for example, webhook nodes that use Port's log reporting API.

Per-node logs

From the node details panel, click See details next to Logs to view only the log entries for that specific node. This is helpful when you want to focus on a single node's behavior without the noise of other nodes.

Workflow runs history table

Port provides a workflow runs history table widget that can be embedded in dashboards and entity pages. The table displays:

Column	Description
Run ID	Unique identifier, links to the run page.
Workflow	Workflow name, links to the workflow editor (for admins).
Workflow ID	The workflow's identifier.
Status	Color-coded label (success, failed, in progress, cancelled).
Source	How the run was triggered (UI, API, EVENT, or TEST).
Who triggered	The user who initiated the run, or "Port" for system-triggered runs.
Start	When the run started.
Completed	When the run finished.
Last updated	When the run was last updated.

All columns are sortable and queryable for filtering.