ACTUAL RECORDING / LOCAL TEST BACK OFFICE
A run stops.
The work stays.
Watch the process stop after the fifth submission, resume from the journal and run the same file again.
10unique submissions received
09verified customers kept
01uncertain item held for review
Follow the recording.
- Start a batch of ten customers.
- Kill the process after the fifth reaches the server.
- Resume: keep four done, hold one uncertain, finish five.
- Run again: skip nine verified customers, hold the same review item.
What this proves.
The local server accepts duplicates. Across this run, resume and rerun, it receives ten submissions with ten unique customer keys. Ritoko uses the saved item journal to avoid resubmitting completed work and to hold the unconfirmed fifth item.
Recorded in real time, without speed-up. The test back office adds a deliberate 700 ms submission delay. This demonstrates interruption handling; it is not a production speed benchmark.
Read the customer onboarding use case Measurements and methodologyFOR YOUR TEAM
Which routine
would you hand over?
Tell us what you repeat, which tools you use and what a successful result looks like. We can discuss whether the workflow is a fit for Ritoko.