Re-run Forecast from Previous Run
POST/api/inventory-forecasting/schedule-runs/:runId/rerun
Re-run a forecast using the configuration from a previous run.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
For scheduled runs with an active schedule, the schedule is queued for execution in the background and the endpoint returns 202 Accepted with type = queued and a tracked_job_log_id; the new run appears in the schedule's run history when it finishes. For manual runs or runs whose schedule was deleted, returns 200 with the configuration_snapshot for manual re-execution.
Request body fields:
- preview (boolean, optional, default false): When true, computes the forecast for inspection only. Skips PO creation (even when the schedule has auto_create_po enabled), skips alerts, and does not advance the schedule's next_run_at. The resulting run is recorded with results_summary.is_preview = true. Has no effect on manual runs (configuration_only path).
Authentication: Requires Bearer token.
Returns 404 if run not found.
Request
Responses
- 200
- 202
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.