Retrieve a specific flow execution
Retrieve detailed information for a specific flow execution.
Fetch a single flow execution by its unique identifier. Returns execution metadata including status, input data, timestamps, and optionally the sequential run number within its flow.
Context:
- Retrieves single execution regardless of status (except deleted)
- Soft-deleted executions return 404 Not Found
- Includes full input data as provided at creation
- Run number calculated on-demand if requested
- Useful for monitoring execution progress
Run Number Calculation:
- When include_run_number=true, calculates sequential position
- Based on creation timestamp among all executions for this flow
- Includes deleted executions (may have gaps in visible numbers)
- Performance: Adds ~10-20ms per request
- Useful for displaying “Run #42” in UI
Use Cases:
- Check status of long-running execution
- Retrieve input data for debugging
- Display execution details in UI
- Audit execution history with run numbers
- Poll for execution completion
Performance Notes:
- Without run_number: ~10ms average response time
- With run_number: ~25ms average response time
- Highly cacheable (status changes infrequently)
Related Endpoints:
- GET /flow-executions - List all executions for a flow
- POST /flow-executions//execute - Re-execute this execution
- GET /task-executions?flow_execution_id= - Get task details
- DELETE /flow-executions/ - Delete this execution
Authorizations
API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOUR_API_KEY
Example:
JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN
Example:
Path Parameters
UUID of the flow execution to retrieve. Must exist and not be soft-deleted.
Query Parameters
Calculate and include sequential run number. Adds ~10-20ms overhead. Recommended for UI display only.
Response
Flow execution successfully retrieved
Flow execution response with optional sequential run number.
Extends FlowExecutionResponse to include an optional run_number field that indicates the sequential position of this execution among all executions for the same flow (including deleted ones).
UUID of the flow definition being executed. References the parent flow that defines the workflow structure.
"550e8400-e29b-41d4-a716-446655440000"
Version number of the flow definition used for this execution. Execution continues on the same version even if flow is updated. Ensures consistency throughout execution lifecycle.
x >= 13
Input data provided when execution was created. Schema is defined by the flow definition. Commonly includes: file_key, document_url, or custom parameters. Structure varies by flow type.
UUID of the organization that owns this execution. Used for access control and data isolation. All executions are scoped to an organization.
"660e8400-e29b-41d4-a716-446655440001"
Current execution status. Possible values: 'queued', 'running', 'in_progress', 'completed', 'failed', 'deleted', 'stale'. Status transitions: queued → running → in_progress → completed/failed. Use 'completed' to indicate success, 'failed' for errors.
"running"
Sequential run number for this execution within its flow. Starts at 1 for the first execution and increments by creation time. Includes deleted executions in count, so visible numbers may have gaps. Only populated when include_run_number=true query parameter is set. Null when not requested to avoid performance overhead.
x >= 142