Smileline
TasksTasksIdPms conflict

The double booking a PMS conflict review is about

For a `pms_appointment_conflict_review` task: the visit the practice system sent, the visits it clashed with (those it was filed against and any it still overlaps on the same practitioner or room), and whether it still clashes. Each visit names its time and timezone, practitioners, room, status, how it was booked and its practice system; its patient only with patient:read and while the patient is not erased. The task closes itself once the clash is gone. Reads only; needs task:read and appointment:read. 404 when the caller cannot read the task; 409 NOT_A_PMS_CONFLICT_REVIEW for any other task.

Loading the API reference…

Undo a just-recorded task outcome POST

Corrects the composite outcome within 60 seconds: cancels the follow-up task, appends reverse transition/activity/correction events, restores the prior projection, reopens the leftover automatic call-backs the outcome closed (409 CONFLICT when one has changed since) and reopens the task (a managers' alert the outcome raised — lead.closed_early, lead.callback_deferred — stays sent) — or, for a `lead_outcome` source task (POST /journeys/:id/outcome), cancels it, so the journey is back to having no open task. Undoing going_ahead returns the journey to the stage it left, active, with its previous agreed value: the won sequences stop, won conversion uploads not yet sent are skipped and the referral it qualified is reversed (partners receive journey.updated). 409 CONFLICT when the value the outcome confirmed (booked's estimate, going_ahead's agreed value) has been changed since; 409 UNDO_NOT_AVAILABLE when the answer also marked a diary visit attended or missed (attended, no_show, or going_ahead on the consultation check): that visit's status is final, and a journey won that way is reopened instead (POST /journeys/:id/reopen); and always for the consultation check's declined and cancelled, whose lead is reopened instead. History is never deleted. Only the user who recorded the outcome can correct it.

Reopen a completed task POST

Moves a task that was simply ticked done back to open: its completion is cleared on the task and kept in its history with the reason (`task_reopened`). Refused with 409 TASK_NOT_REOPENABLE for a task that is not done, one closed by a recorded outcome or a stage move (which keeps its own Undo), a lead's task, and a compliance check's, staff record's, outcome record's or attendance question's task; 409 VERSION_CONFLICT on a stale expectedVersion, so a repeat never reopens twice. The same scope as PATCH applies (404 outside it).