2km.ee

The save that looked like it failed

The request timed out. Did the ERP save it?

Try both decisions on one fictional invoice. This replay runs in your browser.

See the real rehearsal
Invoice DEMO-041 €240.00

Ready to import

The invoice is queued for the destination ERP.

Simulated response timeout

  1. RequestSent
  2. ConfirmationMissing
  3. Write outcomeUnknown

Would you check the recorded outcome or send another import?

The fictional invoice was saved

  1. First writeCommitted
  2. Client responseLost
  3. ERP recordERP-DEMO-01

The run log points to an existing ERP record. Checking it confirms one saved invoice, so the importer can continue.

Two records for one fictional invoice

This branch starts a fresh import without checking the first one. The first write had already succeeded.

Fictional destination records
ERP recordInvoiceTotal
ERP-DEMO-01DEMO-041€240.00
ERP-DEMO-02DEMO-041€240.00

The real rehearsal

Kaupo Karuse, “Hyperspace Migration,” 2km.ee. A 486-record test-company rehearsal completed, including recovery after a lost API response. Reviewed 29 October 2026.