const SSA_SUCCESSOR_SERVICE_WAIT: Duration;Expand description
How long the Entry holds a near-miss SsaRequest while the Exit’s returned data catches up to
the successor boundary.
Absorbs mixer reordering between the returned packets and the SsaRequest they earned — the two
travel the same mixed path, so the request can arrive ahead of the last few packets that
justified it. Nothing longer: a sustained shortfall never reaches this wait, because the gate only
enters it for a request already within one emission window of the boundary.
Comfortably inside the Exit’s max_ssa_delivery_time (20 s by default, batch-scaled), which is
what closes the Session as CommitmentTimeout if no SsaCommit follows. That budget also has to
cover generating the commitments and shipping the burst, so this takes a small slice of it.