Published 22 February 2026, Updated 2 March 2026
Setting inactive is a strong operation: session is considered not completed and requires confirmation.
Reactivation is available only when backend conditions are still valid (for example linked record still valid/not cancelled).
When you choose Set Session Inactive:
- the attendance session is moved to an inactive state
- it is treated as not completed for attendance completion logic
- it is removed from normal active-session handling
- if linked operational records are still open, a warning may indicate follow-up is still required
When you choose Reactivate the session:
- the session is moved back to active/open attendance handling
- this is allowed only if the linked operational record still exists and is still valid
- once reactivated, it can be worked again through normal attendance actions
Practical effect for users:
- inactive sessions appear as inactive and cannot be processed like normal open sessions
- reactivated sessions return to standard workflow and can be closed again correctly