Resources and dispatch
Resource status will not change
Lifecycle changes are recorded and may be blocked by assignments, ownership, or invalid transitions.
This guide applies when
- A resource cannot be archived, retired, or returned to active.
- The status form rejects the change.
What to do
- 1
Check for active incident assignments, orders, swaps, or commitments.
- 2
Choose the intended structured status; a reason is optional unless the page states otherwise.
- 3
Resolve active relationships before repeating the state change.
Still stuck?
Include the page address, local time, signed-in email, browser and device, the exact action taken, and any visible request reference. Remove private information from screenshots.
Never send a password, authenticator or recovery code, API key, payment information, or an unredacted private document.