Optimization
Run control by run id - check a run's status, or cancel it.
Get Run Status
Returns the lifecycle status of a run (queued | running | succeeded | failed | cancelled) for polling. Poll every 2 to 5 seconds: a tight loop gains nothing and will run into the gateway's rate limit (429).
Get Run Status › Responses
The run's current lifecycle status. data.status is queued, running, or a terminal succeeded / failed / cancelled. The response never carries the routes — fetch those from POST /run_results_by_run_id once the run has succeeded.
successThe run lifecycle status returned by GET /problem/{problemId} and POST /run_status. This is what a poller branches on. It is deliberately small — it never carries the routes; fetch those from POST /run_results_by_run_id once the run has succeeded.
Cancel Run
Cancels a queued or running solve. Queued runs are skipped by the worker; running runs are cancelled best-effort.
Cancel Run › Responses
Successful Response
successIndicates if the request was successful
dataThe main response payload. Can be an object, array, boolean, or string.