Recalculate every record under the current policy
What It Does
Recalculation applies saved coverage across existing records when staff request it. Traversal visits contacts before organizations and forces the shared decision routine to reconsider eligible input. Overrides, update locks and records with neither current nor remembered input remain protected. Progress is durable between batches.
The Flow
When Something Fails
A failed batch rolls back without reversing earlier batches. Failure settlement attempts to retain a redacted reason, and queue retries continue from the committed cursor. Successful progress clears that reason. Final failed delivery attempts terminal failed status. If that settlement also fails, the queue can exhaust while the run remains running, requiring recovery outside the regional routes.
An in-request batch failure reports an error after insertion has committed and skips the dispatcher nudge. Scheduled dispatch can still pick up the captured run event. The console does not automatically discover the newly recorded run from the failed response.
Open Design Questions
Recovery for failed settlement and an ambiguous start response needs an explicit implementation plan. Cancellation, examined-count wording and monitoring failures remain unresolved. Policy reads also need consistency protection before completion can support a stronger placement guarantee.