Recover from errors and uncertain outcomes

An interrupted connection can hide a successful admission. Keep the exact original submit_v2_program arguments privately, including the application IDs, typed program, preview token, ordered dependencies and idempotency key. Restore the same verified identity with current write authority.

1. If you know the original jobId, read the durable job first.
2. If the ID was lost, replay the original submit_v2_program request for the sample numeric change. An already-admitted matching batch returns the original jobId, its current status and duplicate: true. The stored admission can be recovered after preview expiry.
3. If no admission exists and the original preview is still valid, replay may admit the original job with duplicate: false. An expired preview can prevent admission. A changed program or dependency order under an existing key can return QUEUE_IDEMPOTENCY_CONFLICT. Stop and reconcile the original request before reviewing any new intent.
4. Follow the recovered job through publication. Verify the sample coordinate and receipt_revision as in the job walkthrough.

This replay path covers facts.numeric.batch and facts.text.batch. Check the catalogue for other operation families. If authority has been removed, restore the intended grant before retrying.