Safety nets
Yessort finds out what happened on a channel by being told: an order was placed, a product changed, a fulfilment was created. That works nearly all the time.
Nearly. Events get dropped, delivery fails, a deploy lands mid-delivery. And a system built on the assumption that every message arrives will be quietly wrong the first time one does not.
So Yessort assumes the opposite. Every important path has a scheduled re-check behind it.
What a safety net does
It re-reads the recent state from the channel and compares it with what Yessort holds. Anything missed is filled in.
They share three properties worth knowing:
They are backstops, not the main route. Events remain the primary path and are what makes things appear quickly. The re-check exists for what the events missed.
They are idempotent. Running one over work already done changes nothing. That is what makes it safe to run them constantly, overlapping, without fear of double-counting.
They overlap on purpose. Each looks back further than the gap between runs — so a missed run, or a slow retry, is covered by the next one rather than falling into a hole.
What runs
Several, covering different paths: orders, fulfilments, availability pushes, the channel's locations, and — on the accounting side — posts that could not be built.
Each is listed with what it heals and how often in safety nets and schedules.
What this means for you
Mostly nothing, which is the point. They need no configuration and no intervention. Most of the time they find nothing, and that is a successful run.
Two things follow that are worth recognising when you see them:
Something appearing later than expected is usually a safety net working, not a fault. An order showing up an hour after the customer says they placed it means the event was missed and the re-check caught it. See when an order arrives late.
They do not surface in the app. There is no screen showing when a re-check last ran or what it found. They are deliberately invisible infrastructure, so the absence of a report is not the absence of the work.
Where they are not the answer
A safety net heals a missed message. It does not fix a wrong setting.
If stock is reaching a channel wrongly because a location is mapped to the wrong site, no amount of re-checking corrects it — the re-check will faithfully re-apply the same wrong mapping. The queues in keeping stock in step and the channel review queue are where genuine disagreements surface.