Fire Batch Run
POST/api/v1/pipelines/:pipeline_id/batch/fire
Start one scheduled occurrence of a batch pipeline. 202 means the run was started, not finished: the warm trigger retries in the background for minutes and a cold pod takes tens of seconds to come up, while the scheduler's DISPATCH_TIMEOUT_S bounds delivery alone. A run already in flight answers 409, which the scheduler records as a dropped occurrence. Cleanup contention is a distinct 503: the scheduler briefly retries that same occurrence through its pod drain.
요청
응답
- 202
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout