The toast that could not fire
A trainer taps Mark All and the whole room's round is recorded. From October 2025, if every one of those saves failed, the app said nothing, because a failed save and a deliberate skip had become the same value.
2 min readMicroGym · Live stage
A session runs on a tablet in the middle of the room. Members move through rounds, and the trainer records each one in a grid, a row per member and a column per movement. Most of the time the numbers are what the grid already suggests, so there is a button for that: Mark All records the round for everyone at once. It is the most-pressed control on the screen that matters most, and it runs on gym wifi.
Two meanings of nothing
Every write goes through one function. It catches any error, logs it to the browser console and returns null. That is a defensible contract as long as every caller reads null as failure. The single-cell dialog does: a null keeps the dialog open and says the save failed. On 23 October 2025 Mark All learned not to overwrite a cell that was already recorded, and the way it skipped a member was to return null. Then, before checking results, it filtered out the nulls as skips. A failed save was now indistinguishable from a member already recorded, and it was filtered out with them.
The check that followed asked whether every remaining result had succeeded, which after that filter could not be false. If every save failed, nothing remained, and the code returned success for an empty list on purpose, because a round where everyone was already recorded is not an error. Two lines further on sat a toast reading Failed to mark all users as completed. Nothing about a failed save could reach it.
What the room would have seen
Nothing, which is the point. The trainer taps, no error appears, and the cells that did not save keep showing a suggestion instead of a record. In a loud room with the next round starting, that looks like done. The error went to the browser console, where the app keeps the last ten to attach to a bug report, and nowhere else. So I cannot say whether it ever happened. The database records the sets that saved. A set that failed leaves no row, and that is the whole difficulty.
The fix
A skip now returns its own marker, and null means only failure. Any failed save makes Mark All report failure, so the toast fires, and the entries that did save still land on screen. The change is fifteen lines smaller than what it replaces. Run over the five cases that matter (all saved, all already recorded, all failed, one failed, a skip beside a failure), the old logic reported success for all five and the new logic reports failure for the three that contain one. It merged on 10 November 2026.
Why it belongs on this page
This is a type error the type system was never asked about. Null meant failure in one function and skip in another, and each was reasonable on its own; the defect exists only where they meet. The live stage's other choice, firing milestone checks without waiting on them, is the same trade made on purpose and written down beside the code: the write must not stall for a side effect. This one was not a choice. It is what happens when one value carries two meanings and the code that reads it has to guess which.