Run Lifecycle
States
A run progresses through the following states:
Configured → Scheduled → Active ↔ Paused → EndedScheduled is optional — runs may go directly from Configured to Active without setting a start time first.
| State | Submissions | Description |
|---|---|---|
| Configured | No | Run created but not yet started |
| Scheduled | No | Start time set; the run begins automatically or manually |
| Active | Yes | Participants can join and submit challenges |
| Paused | No | Operation interrupted (e.g., lunch break); progress preserved |
| Ended | No | Run complete; no further actions possible |
Actions in the dashboard
The RunDashboard provides the following buttons:
| Button | Action |
|---|---|
| Schedule | Sets a start time; transitions to Scheduled |
| Start | Transitions from Configured or Scheduled → Active |
| Pause | Transitions from Active → Paused |
| Resume | Transitions from Paused → Active |
| End | Transitions to Ended (permanent) |
Important notes
- An ended run cannot be restarted. Create a new run for a repeat event.
- At run start, an immutable snapshot of the rallye content is created — later changes to the rallye template have no effect.
- Participants see the current run state in real time in the app.