Leaving a run and breakdown recall
End your shift cleanly, or get pulled out on a breakdown — either way, your work heals back.
When you come off the run
There are two clean ways to come off a run, and in both, the work you were holding flows straight back to the swarm so no stop is left stranded.
Leaving at end of shift
When you're done for the day, leave the run. Any stop still claimed to you is released and the fleet picks it up. You don't hand off a list to anyone — you just come off, and the remaining work redistributes itself among the machines still out there.
Breakdown recall
If a machine goes down mid-storm, the dispatcher can recall it as a breakdown. That's more than marking you offline: the recall reason is logged, and the work you were carrying immediately flows back to the swarm to be reassigned. Nobody has to re-carve routes over the radio to cover the hole you left.
The fleet self-heals
This is the whole point of swarm dispatch. A breakdown or an early departure is one of the exact moments a static route falls apart — someone has to notice, then manually reassign every stop. With Snowmass, the release and reassignment are automatic and near-instant.
Why it matters
Machines break and shifts end — that's normal. Because your outstanding stops always heal back into the swarm, coming off a run is a clean, safe operation, whether it's planned at the end of your shift or forced by a breakdown at the worst possible moment.
Updated 2026-08-09
In this topic
- The real-time ops dashboard
- Proactive failure alerts
- The live interactive map
- Reserve a stop for a machine
- Reopen a completed or skipped stop
- How the live fleet feed stays current
- Join a run and start your shift
- Pause and resume a run
- Device handoff — newest device wins
- Turn-by-turn navigation to your next stop
- Dispatcher FAQ: reading the board during a storm