mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-11-16 17:09:09 +00:00
Withdrawing the land status was all-or-nothing and could be skipped: a refused write stopped revokeLanding and skipped the pause, and a tick that died after blessing left no record, so the next tick recomposed with the status still in success. revokeLanding now attempts every commit, never throws, and records a failed withdrawal in an error event, a note and the rethrown error. The in-flight stage "landing" is saved before the App blesses (the gate: only a batch at that stage pays a status read), and at the end of every live tick a batch stored or marked at that stage that was neither landed nor kept there has each newest land status read and turned into failure where it is success. A manual pause puts such a batch back to the testing stage, so its status is withdrawn until it lands after the resume.