Update a task
409 VERSION_CONFLICT on a stale expectedVersion; 409 COMPLIANCE_TASK_NEEDS_ENTRY when a compliance check's task would change status or kind (it closes by recording the check; assignee, due date, priority, title and note stay editable); 400 TASK_KIND_RESERVED when any other task would become compliance_check or staff_record_expiry, or a staff record's reminder would change kind. The check or staff record a task belongs to is never editable here. A dentist, hygienist or nurse gets 403 OWN_TASKS_ONLY when the edit would link a journey, give the task a kind they may not create, or leave the task no longer theirs. Linking a journey makes the task `crm` work; a reassignment or that move answers 422 TASK_ASSIGNEE_CANNOT_SEE when the assignee is a dentist, hygienist or nurse, who could never see a `crm` task. A new assignee must be a live member (422 ASSIGNEE_SUSPENDED); a task already with a suspended member keeps them until reassigned. Moving a `flexible` retry's `dueAt` by hand makes it a `kept` call-back (the time a person chose), which nothing automatic moves or closes.
Loading the API reference…
Get a task GET
Previous Page
Cancel an open task with a reason POST
Moves an open task to cancelled and keeps the reason in its history (`task_cancelled`). 409 TASK_NOT_OPEN when it is not open; 409 COMPLIANCE_TASK_NEEDS_ENTRY for a compliance check's task, which closes by recording the check (or disabling it); 409 TASK_KIND_RESERVED for an outcome record; 409 VERSION_CONFLICT on a stale expectedVersion. The same scope as PATCH applies (404 outside it).