Replay Execution
Replay a previous pipeline execution.
Full replay coordinator:
- Creates a new execution record linked to the parent
- Starts routes via OrchestratorManager (skip init_message)
- Publishes replay messages from source storage to target route
For cross-pipeline replay, provide config_id in the request body to use a different pipeline’s routes. Storage reads from the parent execution.
Args: execution_id: Parent execution UUID or tag to replay from request: Replay request with from_stage, to_route, and replay source service: Execution service (injected) container: Service container for manager, storage, queue, route resolver
Returns: New execution record for the replay
Raises: HTTPException: 404 if parent execution not found, 400 if route/stage invalid, 503 if services unavailable
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”Request to replay a pipeline execution.
The execution to replay is identified by the execution_id path parameter. Server creates a new execution, starts routes, and publishes replay messages.
For cross-pipeline replay, provide config_id to use a different pipeline’s routes instead of the parent’s. Storage reads from the parent execution.
object
Type of replay
Pipeline stage to replay from (e.g. ‘markdown_segmented’)
Target route name (e.g. ‘embedding_generator’)
Responses
Section titled “ Responses ”Successful Response
Pipeline execution response.
Storage paths use execution id (UUID v7) directly.
object
Execution UUID (used for storage paths)
Configuration ID
Current status
Start timestamp
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