agent scheduled a 4-person panel chain and one decline broke the chain - no re-plan triggered and three interviewers...
Fixes panel schedulers where one decline strands the rest of the chain. Use when each panel leg is an independent event with no shared state. Key trigger: interviewers sitting in an empty call because a decline never propagated.
TL;DR: Treat a panel as one transaction: any decline pauses the whole chain and triggers a re-plan before anyone joins a call. The three interviewers sat in an empty call because each leg was an independent event and the decline never propagated. Hold the remaining legs the moment one breaks.
agent scheduled a 4-person panel chain and one decline broke the chain - no re-plan triggered and three interviewers sat in an empty call- Find where declines are processed and check whether sibling legs are notified.
Expected: the decline updates one event and nothing else; the other three legs stay confirmed.
- On any decline, immediately mark the panel "needs re-plan" and set the remaining legs to a pending state.
Expected: the other interviewers see the panel as on hold, not as a confirmed call.
- Notify the recruiter with the broken slot and two alternative slots for the declined leg.
Expected: the recruiter gets one actionable message, not four separate decline notices.
- Only re-confirm the chain when all four legs are re-booked; send updates, not duplicate invites, for legs that keep their slots.
Expected: interviewers whose slots did not change get a single update.
- Add a pre-call check two hours before the first leg: verify all four events still exist and are confirmed.
Expected: a broken chain discovered late still cancels cleanly instead of wasting the panel's time.
Use this when
- Panel interviews are booked as separate events with no shared state.
- A decline in one leg leaves the others running.
- Interviewers join calls where the candidate or a colleague never shows.
Not for this skill when
- Each interviewer meets the candidate independently and legs are genuinely standalone.
- The panel is optional-attendance (only some interviewers required); model required vs optional instead.
- The decline was the candidate withdrawing entirely (cancel the whole loop, do not re-plan).
Variant phrasings
- one decline broke the panel and nobody re-planned
- interviewers sat in an empty call after a panelist declined
- panel chain kept going after one leg cancelled
- decline did not propagate to the rest of the interview panel
Why it happens
The scheduler modeled a panel as four independent bookings, but a panel is one coordinated commitment. A decline is a local event in that model, so it stayed local. The remaining legs had no way to know the chain was broken because no shared state existed to carry the news. Coordination has to be explicit: one panel object, one status, all legs subscribed to it.
Edge cases
- A decline arriving minutes before the first leg: the pre-call check is the last line of defense. Cancel loudly rather than letting people join.
- A decline with a proposed new time: treat it as a re-plan request for that leg, but still hold the chain until all legs confirm.
- Partial panels where only some interviewers are required: define required vs optional per panel so an optional decline does not halt everything.
- Candidate declines vs interviewer declines: the candidate declining ends the loop; an interviewer declining re-plans it. Route on who declined.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_5NibUN3yUvIEaSZfZlm2Yg
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.