Activity Type and Outcome Availability

The Lifecycle

Availability separates retirement from removal. A retired choice remains valid on interactions that already carry it. Deleted describes the absence of configuration after its removal.

Transitions Explained

The structured rows distinguish whole-type deletion from removal of an individual result during a type save. Baseline types remain present, but unused results belonging to them can be removed. Reapplying defaults adopts existing entries rather than overriding local administration.

What Cannot Happen

New interactions cannot select inactive activity configuration, and references protect entries from deletion. Task configuration has a separately recorded inconsistency: inactive task types and queues continue accepting new work. This examination retains that planning question.

Concurrency and Timing

Version checks protect type editing and result replacement. Database references arbitrate deletion against concurrent use. Removal of an entire type has no read-version argument.