Safety nets and schedules

Yessort re-checks its own work on a schedule rather than assuming every event arrived. Background in safety nets.

Channel safety nets

Re-check	Runs	Looks back	Heals
Orders	Hourly	3 hours	Orders the channel's event did not deliver. Without it a sale has no order, no reservation and no invoice
Fulfilments	Hourly	26 hours	Fulfilments the channel reported that did not arrive
Availability	Hourly	—	Stock pushes the event path dropped, and stale overwrites from a retry
Availability drift (sample)	Nightly	—	Nothing. It reports — comparing a subset of what the channel displays against what Yessort holds
Availability drift (full)	Weekly	—	Nothing. Reports, over every live listing
Locations	—	—	Discovers channel locations nobody has mapped, and notices ones the channel deactivated

Accounting safety nets

Re-check	Runs	Heals
Deferred posts	Nightly	Accounting entries that could not be built. Replays them once the missing configuration exists — see hold, don't drop

Reading the windows

The window is wider than the interval, deliberately. The order re-check runs hourly over three hours, so every order is covered three times. A skipped run or a slow retry is picked up by the next one instead of falling through.

The fulfilment window is much wider at 26 hours because fulfilment volume is lower, so looking back further costs little. The order window is kept narrower because re-reading a day of order history every hour would be expensive for a busy store.

Repairing versus reporting

Worth keeping apart, because the two look similar in this table:

Repairing re-checks fill in what was missed — orders, fulfilments, availability pushes, deferred accounting posts. They change things.

Reporting passes only compare and record. The availability drift passes change nothing at all; they exist so a divergence is visible. See keeping stock in step.

What none of them do

Fix a wrong setting. A safety net heals a missed message. A location mapped to the wrong site will be re-applied, wrongly, every time — because as far as the re-check is concerned that is the configuration.

Genuine disagreements surface in the queues instead: reconcile reviews, the channel review queue, and the accounting queues.

Visibility

None of these appear in the app. There is no screen showing when one last ran or what it found — so a missing report is not a missing run.