Skip to content

Rewind a completed storm: replay, why stops moved, and what-ifs

Every completed storm is captured automatically. Replay it, read the engine's own account of why stops moved, and re-run it with a different plan.

Simulations Updated 2026-08-17

Captured automatically — and kept

When a storm completes, Snowmass captures a Rewind of it on its own: a replayable record built from the durable service-visit timeline — when each stop was entered, finished, and by which machine. It does not depend on GPS pings (which are pruned after 72 hours), so a Rewind survives forever. Open Rewind in the sidebar to see your storms, newest first.

The replay

A Rewind plays back with the same scrubber as a simulation: machines fan out from the depot, stops flip from pending to done, and a stats summary (duration, stops completed and skipped, throughput per hour) sits alongside. Machine movement between stops is reconstructed, so it's a faithful retelling of the storm — not a GPS trace.

Why stops moved

During a live storm, the engine sometimes reassigns a stop from one machine to another to heal a problem. The Rewind lists those moves in order, with the reason — so "why did that stop change vehicles at 2 a.m.?" has an answer you can point to.

What-if re-runs

From the same page you can launch a counterfactual: the same real stops, re-run through the engine with a different starting direction or vehicle count (defaults match how the storm actually ran). Past counterfactuals stay listed so you can compare. They are advisory — a synthetic pace with no weather or breakdowns, a directional hint rather than a promise.


← All help topics

Updated 2026-08-17