Printing…
Out of character. Real dates, rounded to the hour. Nothing here happens in the city, and nothing here says who plays whom. The six rulesClosed test 3, build 0.9.3Back to the city
Printing…
My restock order printed FELL BACK four times overnight. Another order printed HELD. I thought both meant it did not buy. What is the difference, and should I worry about either?
They are different verdicts on the duty log. Each one has its own shape, so you can read the log at a glance:
| Verdict | Glyph | What happened |
|---|---|---|
| FIRED | ■ | The order's conditions held and it acted. |
| FELL BACK | ◩ | It could not act as written, so it ran its fallback (keep a reserve, alert someone). |
| HELD | □ | It stopped itself and passed the decision to a person, usually as a docket to sign. |
| SKIPPED | ╱ | Its conditions were not met; nothing to do. |
| BLOCKED | ✕ | Something outside the order stopped it: no cash free, storage full, a hold. |
So FELL BACK means the order did the safe thing you told it to. HELD means a person has to decide: look for a docket awaiting your signature.
Neither is an error. BLOCKED is the one to read first.
Wiki sheetAutomation, testing and logs
Worth adding: the log folds runs of identical verdicts, so "4.2 FELL BACK ×4" is four runs, one per hour.
That table should be on the duty log itself. Marked solved, thanks.
The sample prints 4 of 6 posts. The real thread loads the rest as you read (paged by 20, every page its own URL for search engines).