Activity Status

The Lifecycle

The three persisted statuses describe an interaction’s progress, while Deleted describes absence of its live row. Creation accepts a selected status or uses the type’s default. The console proposes a scheduled entry for a future instant unless the user has already selected a status.

Transitions Explained

Any persisted status can be changed to either other status through an ordinary edit. Activities have no separate completion or cancellation command. The structured transition rows give save requirements, timeline placement and revision effects.

What Cannot Happen

A removed interaction cannot be restored through the API. Write locks and field requirements can prevent an otherwise supported status change. Passing the scheduled instant changes its computed overdue display without updating the stored status.

Concurrency and Timing

Read versions protect ordinary edits from overwriting a newer save. Status copies and revision capture share the transaction. Deletion uses locking but takes no read version, so it has a different conflict contract.