Trigger a schedule immediately
Trigger an immediate run of a scheduled scan. Stored Supply Chain schedules require the Enterprise Supply Chain entitlement. When a pentest schedule fires, the open issues of its earlier runs also get separate retest scans (up to 50 issues each), in their own sandboxes and with their own agents, so the new pentest does not know the old issues. Each open issue is retested once, in a run scoped like the newest earlier run whose scope still reaches it. An open issue that the retest scan does not reproduce is set to fixed. Read the retest scans through GET /scans/{scanId}/retests on each earlier run that has open issues. A 200 acknowledges durable queue acceptance; later execution failures are reported in the schedule’s run health and are never silently launched a second time. Manual schedule fires support the optional Idempotency-Key contract used by scan creation: reuse the exact same key only to retry the same schedule trigger after a lost or ambiguous response. Replay and in-progress responses are returned only after current authorization against the schedule succeeds.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Headers
Opaque caller-generated key for at-most-once billable scan creation; use a high-entropy value such as a UUID. Reuse the exact same key only when retrying the exact same request. Completed keys are retained for at least 24 hours; an unfinished accepted worker receipt may be held longer until its downstream queue horizon is safely reconciled. A completed failure is terminal for that key. Keyed terminal responses echo Idempotency-Key and set Idempotency-Replayed to true only when returning a stored outcome.
1 - 200^[A-Za-z0-9][A-Za-z0-9._:/=-]{0,199}$Path Parameters
ID of the schedule. Use the id field of a schedule from listSchedules.
Response
The manual fire was durably accepted by the queue. This does not assert that the asynchronously launched scan has completed successfully.