Execution & Logs

Run workflows, track execution status, inspect per-step logs, and diagnose failures.

Running a Workflow

There are two ways to execute a workflow:

Manual Execution

Click the Run button in the editor toolbar. The workflow executes immediately using the trigger configuration. For webhook triggers, the mock request payload (if set) is used as input.

Webhook Execution

Send an HTTP POST to the workflow's webhook endpoint with an Orchestrator API key:

curl -X POST "https://orchestrator.skytells.ai/api/workflows/{workflowId}/webhook" \
  -H "Authorization: Bearer wfb_your_key" \
  -H "Content-Type: application/json" \
  -d '{"event": "order.created"}'

See Webhooks for the full reference.

Execution Status Model

Each workflow run creates an execution record with one of these statuses:

Status	Meaning
`pending`	Execution created, not yet started
`running`	Workflow is actively executing steps
`success`	All steps completed successfully
`error`	One or more steps failed
`cancelled`	Execution was cancelled

Each individual step within an execution also has a status:

Status	Meaning
`pending`	Step not yet reached
`running`	Step is currently executing
`success`	Step completed successfully
`error`	Step failed with an error

Viewing Execution History

Open the Runs panel (tab in the right sidebar) to see recent executions for the current workflow.

Each execution entry shows:

Status (pending/running/success/error)
Start time and duration
Error message (if failed)

Click an execution to expand it and see per-step details.

Inspecting Step Logs

Each step log entry contains:

Field	Description
Node name	The display label of the step
Node type	`trigger` or `action`
Status	Step execution status
Input	The parameters passed to the step (redacted)
Output	The data returned by the step (redacted)
Error	Error message if the step failed
Duration	How long the step took (in milliseconds)
Timestamps	Start and completion times

Execution logs automatically redact sensitive data — API keys, authorization headers, credentials, and other private fields are stripped from input/output before storage.

Diagnosing Failures

When a workflow fails:

Open the failed execution

In the Runs panel, click the execution with an error status.

Find the failing step

Look for the step with a red error status. Its position in the list tells you where execution stopped.

Check the error message

The step's error field contains the failure reason — this could be an API error from the provider, a network issue, or a configuration problem.

Inspect input data

Check the step's input to verify that template variables resolved correctly and the data from upstream steps was what you expected.

Fix and re-run

Correct the issue (fix the config, update the integration, adjust the upstream step) and run the workflow again.

Common Error Patterns

Error	Cause	Fix
Integration credentials missing	Action node has no integration selected	Attach an integration in the node config
401 Unauthorized	Provider API key is invalid or expired	Update the integration credentials
Template variable not found	Referenced a node that doesn't exist or has no output	Check node connections and variable syntax
Condition expression invalid	Expression uses disallowed syntax	Use only supported operators — see Variables & Conditions

Execution Data Lifecycle

Execution records: The 50 most recent executions per workflow are returned by the API.
Execution logs: Per-step detail available via the logs endpoint.
Clearing logs: You can delete all execution logs for a workflow from the API or settings.

Webhook Execution Response

Webhook-triggered executions return immediately with:

{
  "executionId": "exec_abc123",
  "status": "running"
}

The workflow continues executing asynchronously. Use the execution status or logs endpoints to check progress. See API Reference for details.