Skip to content

Execution Log

The Execution Log records every orchestration execution that runs in your enterprise. Use it to monitor recent activity, investigate failures, and audit data flows.

Accessing the Execution Log

Navigate to BUILD > Orchestration Runner and select the Execution History tab. You will see a table listing all recent executions.

What the Log Shows

Each row in the Execution Log represents a single execution of an orchestration:

Column Description
Execution ID A unique identifier for this execution (click to view the trace)
Orchestration The name of the orchestration that was executed
Status The overall result: Success, Failed, Partial, or Running
Started When the execution began (timestamp)
Duration Total execution time in milliseconds
Steps Number of steps completed vs total (e.g., "5/5" or "3/5")
Triggered By How the execution was started: Manual, Scheduled, API, or Event

Execution Statuses

Status Colour Meaning
Success Green All steps completed successfully
Failed Red The execution was aborted due to a step failure
Partial Amber Some steps succeeded and some failed, but the orchestration completed (because error handling was set to "continue on error")
Running Blue The execution is currently in progress

Filtering and Searching

Use the filter controls above the table to narrow the results:

By Status

Filter to show only executions with a specific status:

  • All
  • Success
  • Failed
  • Partial
  • Running

By Orchestration

Select a specific orchestration to see only its executions. This is useful when investigating issues with a particular workflow.

By Date Range

Set a start and end date to view executions within a specific time period. Common quick-select options:

  • Last hour
  • Last 24 hours
  • Last 7 days
  • Last 30 days
  • Custom range

By Trigger Type

Filter by how the execution was started:

  • Manual (triggered by a user from the UI or API)
  • Scheduled (triggered by a cron schedule)
  • Event (triggered by an incoming webhook or event)

Execution Detail

Click any execution row to open its detail view, which shows:

Summary

  • Execution ID
  • Orchestration name and version
  • Start time, end time, and total duration
  • Status
  • Input parameters used for this execution

Step Results

A list of every step in the execution with:

Column Description
Step Step name
Type API Call, Transform, Conditional, or Error Handler
Status Success, Failed, or Skipped
Duration How long the step took
Error Error message (if the step failed)

Click any step to drill into its Execution Trace with full input/output payloads.

Re-Running a Failed Execution

If an execution failed and you want to retry it:

  1. Open the failed execution's detail view
  2. Click Re-Run
  3. The orchestration executes again with the same input parameters
  4. A new execution is created (the original failure is preserved for audit)

Fix Before Re-Running

Before re-running, check the failure reason. If it was a credential issue, update the credentials first. If it was a transient network error, a re-run may succeed immediately.

Re-Running with Modified Parameters

If you need to change the input parameters before re-running:

  1. Open the failed execution's detail view
  2. Click Re-Run with Changes
  3. Edit the input parameters in the JSON editor
  4. Click Execute

Execution Retention

Execution logs are retained according to your enterprise's retention policy. By default:

Data Retention
Execution metadata (ID, status, times) 90 days
Step results (status, duration, errors) 90 days
Input/output payloads 30 days

After the retention period, data is permanently deleted. See Retention Policies for configuration options.

Archival

If you need to retain execution data beyond the retention period, export it using the dashboard export feature before it expires.

Bulk Operations

Exporting Execution Data

  1. Apply your desired filters
  2. Click Export
  3. Choose CSV or JSON format
  4. The export includes all filtered executions

Purging Old Executions

Enterprise administrators can purge execution data older than a specified date:

  1. Click Purge
  2. Select the cutoff date
  3. Confirm the purge

Irreversible

Purging execution data cannot be undone. Ensure you have exported any data you need before purging.

Best Practices

  1. Monitor daily: Check the Execution Log each day for failed executions
  2. Set up alerts: Do not rely on manual checking -- configure alert rules for execution failures
  3. Investigate patterns: If the same orchestration fails repeatedly, investigate the root cause rather than re-running each time
  4. Use filters effectively: Narrow down to the specific orchestration and time range to find issues quickly
  5. Export for compliance: If your organisation requires audit trails, export execution data regularly

Next Steps