POST /api/v1/cloud/environments/{environment_id}/work/{work_id}/ack
Acknowledges a delivered work item and moves it from queued to starting. Workers should ack after poll and before executing the Session work.
Ack is safe to retry for items already in starting or active. It conflicts for stopping or stopped items.
Path parameters
| Parameter | Type | Description |
|---|---|---|
environment_id | string | Environment ID with the env_ prefix |
work_id | string | Work item ID with the work_ prefix |
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer $QODER_PAT |
Worker-ID | No | Stable worker identity. If poll stored a different Worker-ID, ack returns 409 |
Example request
Example response
HTTP 200 OKResponse fields
Returns the acknowledged Work item object.Errors
| HTTP | Type | Trigger |
|---|---|---|
| 400 | invalid_request_error | The Environment is not self_hosted |
| 401 | authentication_error | PAT invalid or expired |
| 403 | permission_error | Not authorized for this operation |
| 404 | not_found_error | Environment or work item not found |
| 409 | invalid_request_error | Work item was claimed by another worker, changed state concurrently, or is stopping/stopped |
Notes
- After ack, the first heartbeat usually uses
expected_last_heartbeat=NO_HEARTBEAT. - Ack triggers an immediate dispatch pass so work can proceed without waiting for the next dispatcher tick.
Related
Cloud environment setup
Choose the container, network, and dependencies your agent runs in.