Execute detached replay
Replay stored pipeline outputs from a previous execution to any target route.
This creates a new execution context with:
- New execution_id (UUID v7)
- New replay_batch_id (UUID v7) for grouping replayed messages
- Unique correlation_id per message for lineage tracking
The replay operation:
1. Lists objects at the source prefix (execution_id/stage/path)
2. Filters out .meta.json sidecar files
3. Publishes each object to the target route's inbound queue
4. Puts execution_id and replay_batch_id in message METADATA
5. Puts object_key in message payload for downstream adaptersRequest Body required
Section titled “Request Body required ”Request model for detached replay API.
Semantic fields for replaying stored outputs to a target route.
object
UUID of the source execution to replay from
Pipeline stage name (e.g., ‘boost/compacted’, ‘markdown_converted’)
Target route name to replay to
Responses
Section titled “ Responses ”Successful Response
Response model for detached replay API.
Contains counts and status of the replay operation.
object
New execution UUID for replayed messages
Source execution UUID
Source pipeline stage
Target route name
Target queue that received messages
Total objects found at source prefix
Objects successfully published
Objects that failed to publish
Overall status of the replay operation
UUID for grouping all replayed messages
Bad request
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.
Resource not found
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.
Validation Error