POST /api/v1/forward/schedules/{schedule_id}/run
Creates a Schedule Run immediately without changing the Schedule’s trigger policy. The endpoint returns when the Run record is created, not when execution finishes.
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <PAT> |
Content-Type | No | application/json if a body is sent. |
Idempotency-Key | No | Optional idempotency key for unsafe requests. |
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
schedule_id | string | Yes | Forward Schedule ID. |
Example request
Example response
HTTP 200 OKResponse fields
Returns the created Schedule Run object.Errors
| HTTP | Type | Code | Trigger |
|---|---|---|---|
| 401 | authentication_error | authentication_required | PAT invalid or expired. |
| 404 | not_found_error | schedule_not_found | Schedule does not exist. |
| 409 | invalid_request_error | schedule_archived | Schedule is archived. |
| 409 | invalid_request_error | schedule_not_active | Schedule is paused. |
Notes
- If the Schedule has reached
execution.max_concurrent_runs, Forward still creates a Run withstatus=skippedanderror.type=concurrency_limit_reached. - Poll Get Schedule Run until
statusiscompleted,failed, orskipped.