Using Headwind
When a review stops
Finished steps are saved. Short failures are retried automatically; longer ones wait for you.
Review states
| Waiting for the worker | Queued. The worker picks it up within a few seconds if it's running. |
|---|---|
| Running | A worker holds a 2-minute lease on the review and renews it while working. |
| Retrying after an error | A step failed. The worker checks what was already saved, then tries again, up to 3 attempts. |
| Partly done | Some steps finished, then it stopped (for example, the review's credit budget ran out). Finished steps are kept. |
| Stopped | It couldn't finish. Saved results are kept. |
Retry unfinished steps
On a partly done or stopped review, Retry unfinished steps resumes from the step that stopped. It won't run if another review is in progress, or if the imported data changed since the review was planned.
No double writes
Before resending a cfo.ai write whose answer was lost, Headwind reads cfo.ai first. If the values are already there, it only records the readback.