hardScenarioDesignSeniorStaffLead
Three days of your visibility events are unrecoverable and freight is still moving. How do you re-establish where everything is?
7 min readUpdated 2026-08-15Target archetype: Enterprise Captive
Answer
Short answer
Rebuild rather than reconstruct: most of those events still exist in carrier systems, EDI mailboxes and handheld queues, so re-ingest them idempotently by date range, then close the residual gap with physical observation at yards and terminals.
Track and trace matters here because the three days of visibility events are answer has to show the boundary, not just the happy path.
Was this answer helpful?
Likely follow-ups
- Which of your carriers can serve a date-range replay, and what do you do about the ones that cannot?
- A re-ingested event arrives after a later event you already applied. What does your projection do?
- How would you prove afterwards which parts of the rebuilt history were observed and which were inferred?
- What would you archive today, cheaply, so that this recovery is a day rather than a fortnight?
Related questions
- Design a platform that runs agent tasks for hours and pauses for a human to approve risky steps.hardAlso on idempotency6 min
- You must ingest all of English Wikipedia every day, and the source does not want to be hammered. What runs, how often, and what do you do about the run that fails at hour six?hardAlso on idempotency6 min
- An Android app queues actions while offline. After the process is killed and restarted, some actions sync twice and the user sees duplicate orders. How do you design the fix?hardAlso on idempotency4 min
- Your services talk through events and one consumer has been down for an hour. What has it missed, and how does it catch up?hardAlso on idempotency6 min