The engine writes a have's detail cut to its head and tail, and the
indexer's live hold (315 bytes) lost "the recovery module could not be
asked" there, so its cause read as a failed point: its wait was cleared and
the operator asked, the opposite of H-A-180. The cause is now read from the
wait's words, which the have keeps whole; the detail only for a hold with no
wait.
Builds: design 47 H-A-180
A module held because the recovery module could not be asked kept that hold
across the engine's start as if it waited for the operator's answer, while
its have carried a wait, so the assigner never raised that ask: the hold was
for good (the indexer on the control-node). The engine now judges such a hold
again at its start and at every change of the placements: with no holder of
mesh-recovery placed it moves the module without a point (H-A-177), with one
placed it asks the point once more. A point a holder answered and failed is
held as a failed backup, with no wait, so the assigner raises the operator's
ask (back up again or skip); an older hold of that kind written with a wait
is written again without one at the start.
Builds: design 47 H-A-180, H-A-177, ADR 0568 §4, G-14 (a snapshot-kept that ends failed holds as a failed backup), A-453