Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. Gera: when a customer's guest card gets stuck on hold, should engineering be paged once when the hold starts, or again every so often while it stays held?
The full question, as raised
Should a customer's guest card that is HELD (card-held, #19576) ever re-page engineering after the one page at hold start — e.g. after 12h or 24h still held — or is once enough? #21879 makes the 10-minute stuck sweep honour the hold (paged once), which is what the hold's own contract says; today the sweep contradicts it and re-pages the same held row every ~4th pass.
Why, and what was tried
The session raising this recommends: Page once when the hold starts, then stay quiet The hold already paged guest_card.create_held once with a per-intent fingerprint; the org outage alarm and raiseOutage still fire on a login refusal (positive control in #21879); a held card is by design never lost, it stays pending. The repeated 'stuck' page was noise: 4 pages today on three Fairhaven rows with 19-20 attempts (propflow-prod PMS_WRITE_INTENT#gc:create_card:66a927c7-…, cf62b1c2-…, de06842c-…). Option 2 is a small follow-up PR on top of #21879; option 3 means closing #21879 and rewriting the hold's doc. Tried first, unsuccessfully: Fable read both contracts (guest-card-outbox-drain.ts CARD_HELD_PARK_REASON doc: 'paged ONCE when the hold starts'; guest-card-outbox.ts findStuckPendingIntents: no card-held knowledge), the cron route ordering (drain then sweep), and the three live prod rows; it is an alerting-policy call for a customer's held card that no doc settles, so Fable could not decide it from code.