Update task queue
/v1/task-queue/items/{itemId}
Signed-in sessionLaunch key product.workOperation task_queue_update
A person puts work in their own queue: a project task (with a priority, a due time and an optional deadline) or a briefing schedule that their agents write.
Headers
- X-Specify-Account-IdstringRequired
- The account the request acts in.
- X-Specify-Service-Tenancy-IdstringRequired
- The service tenancy the request acts in.
Path parameters
- itemIdstringRequired
Body
- instructionsnull | string
- priority"high" | "low" | "normal" | "urgent"
- dueAtnull | number
- deadlineAtnull | number
- expectedAuthorizationVersionstring
- expectedVersionnumberRequired
Returns
- versionnumberRequired
- createdAtnumberRequired
- updatedAtnumberRequired
- attachmentsTargetobject | any
- itemIdstringRequired
- kind"briefing" | "task"Required
- titlestringRequired
- priority"high" | "low" | "normal" | "urgent"Required
- state"awaiting_approval" | "cancelled" | "claimed" | "completed" | "failed" | "missed" | "queued"Required
- availableAtnumberRequired
- dueAtnull | numberRequired
- deadlineAtnull | numberRequired
- source"manual" | "run_now" | "schedule"Required
- projectsobject[]Required
- tasknull | objectRequired
- podcastfalse | null | trueRequired
- holdernull | objectRequired
- attemptsnumberRequired
- maxAttemptsnumberRequired
- lastErrornull | objectRequired
Errors
400, 401, 403, 404, 409, 429 and 503 return {"error": {"code", "message", "correlationId"}}. A call without a valid credential gets 401 before its input is checked, and so does an address that is not an operation: 404 and 400 come only once the credential is accepted. Public operations answer without one.