Skip to content
Astera Technology

Withdraw waitlist offers when a session becomes unavailable

Close pending invitations and keep accepted bookings on the operator-cancellation path.

Partition pending offers and confirmed bookings

Synthetic rule: an operator cancels the session at 16:00. Pending offers become withdrawn, not expired or declined. Offers already accepted have produced confirmed bookings and follow the booking cancellation policy. Waiting entries close because this session will not run; moving them elsewhere requires a new choice.

Synthetic withdrawn-offer register
RecordAt 16:00New stateSession action
W-U1Pending offer; no session heldOperator withdrawnNone
W-U2 / B-U2Accepted; booking holds 1Booking operator-cancelledReturn held 1 under policy
W-U3Waiting; no offerSession closedNone
Download editable CSV ↓

Stop invitation work before closing records

  1. Mark the session unavailable and stop issuing further offers.
  2. Withdraw pending offers and release their place holds.
  3. Cancel confirmed bookings through their own policy and close waiting entries with the session reason.

If acceptance and cancellation arrive close together, use the recorded final state to decide which path applies; never both withdraw an offer and independently return an unheld session.

How many session returns arise from the three records?

Show the worked answer

One, for B-U2. W-U1 and W-U3 never held package sessions, so their closure creates no return.

A withdrawal reason belongs to the operator action. Preserve it so later re-entry does not look like repeated customer refusal.

Related resources