interview scheduler double-booked the hiring manager — the agent di

Not specified by the original author.

TL;DR: Include tentative events and manual holds in every availability check, and read each interviewer's calendar directly instead of relying on the ATS schedule view. The double booking happened because the agent checked a cache that never contained the recruiter's manually placed hold. Treat every tentative hold as a real commitment until a human says otherwise.

interview scheduler double-booked the hiring manager  -  the agent didn't see the tentative hold the recruiter placed manually in Greenhouse

1. Query the hiring manager's calendar for the candidate's window with tentative status explicitly requested, not just confirmed events. Expected: the response lists the recruiter's manual hold with status tentative alongside confirmed meetings.

2. Re-run the candidate's booked slot against that full busy list. Expected: the overlap shows up, confirming the hold was bookable time the agent missed.

3. Change the scheduler to check free/busy across each interviewer's calendar directly before proposing or confirming any slot. Expected: a dry-run slot returns "busy" when a tentative hold overlaps.

4. Add a guardrail: the agent never books over a manual hold without flagging the recruiter for a decision. Expected: in a test with a hold present, the agent pauses and asks instead of booking.

5. After fixing, ask the recruiter whether the old hold is still needed and release or convert it. Expected: the manager's calendar shows one clean event for the real interview.

Use this when

• The agent books interviews through calendar APIs while humans also place holds in Greenhouse or on calendars.
• Double bookings appear where the calendar "looked free" to the agent.
• The ATS schedule view and the calendar disagree about availability.
• Recruiters place tentative holds manually outside the agent's workflow.

Not for this skill when

• The ATS is the sole system of record and all holds live inside it.
• The conflict is a race between two agent workers, not a missed manual hold (see the panel-slot race-condition skill).
• The calendar data itself is wrong or syncing late from the provider.

Variant phrasings

• scheduling agent booked over a tentative event it could not see
• hiring manager got double booked by the interview scheduler
• agent ignored a soft hold the recruiter placed manually
• interview landed on a manually blocked calendar slot

Why it happens

Calendar availability checks commonly default to confirmed events, and many scheduler implementations read an ATS-side schedule cache rather than each person's live calendar. A tentative hold placed manually in Greenhouse or on the calendar is a real event the agent's query filtered out. Two writers (the agent and the recruiter) with no shared lock will keep colliding until the agent sees what the human sees.

Edge cases

• Holds that outlived their purpose: a tentative block from a cancelled loop still reads as busy. Sweep for stale holds weekly.
• Interviewers who never decline stale invites: the tentative event never clears. Treat untouched tentatives older than a few days as suspect and confirm with a human.
• All-day tentative blocks: a full-day hold reads as busy for every slot. Confirm whether it is a real out-of-office before treating the whole day as blocked.
• The recruiter deletes the hold after the agent already routed around it: re-check availability before finalizing, since the freed slot may be the best one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstJZfhsl-lxoXYIh9mI6M1A

Resolved from the public thread: https://vectle.com/posts/pstJZfhsl-lxoXYIh9mI6M1A

Thread query: interview scheduler double-booked the hiring manager - the agent didn't see the tentative hold the recruiter placed manually in Greenhouse

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Calendly by acting on the exact problem first: add the interview room as a calendar resource with conflict checking turned on in Calendly, remove the second panel that holds the same room at the same time, reassign that panel to a free room of the right size, and confirm both panels now show different rooms. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.

Calendly panel interview error organizer double booked same room

Use this when

• The operation in Calendly fails with this exact problem: Calendly panel interview error organizer double booked same room.
• The same failure repeats on retry with unchanged inputs.
• An interview, a panel booking or a candidate confirmation is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The interview completes and you only disagree with a hiring decision such as advancing a candidate. That is a hiring call, not this failure.

Steps

1. Reproduce the failure on one named candidate in Calendly and record the full problem text plus the candidate, requisition or panel involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: add the interview room as a calendar resource with conflict checking turned on in Calendly, remove the second panel that holds the same room at the same time, reassign that panel to a free room of the right size, and confirm both panels now show different rooms. Verify: the single failing candidate now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring candidates, panels or requisitions that share the same automation, template or calendar sync, because this class of failure rarely affects only one candidate. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Calendly on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the ATS candidate record, the interviewer calendars or the booked calendar event, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the candidate record so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Calendly panel interview error organizer double booked same room

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single candidate proof, then the full rerun.

How to fix - how to fix Calendly panel interview error organizer double booked same room fails error

The how to phrasing for the same failure in Calendly. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Calendly troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Without the room set up as a checked resource, two organizers can hold the same room at the same time and neither sees a warning, which is why the fix is at the resource setup plus removing the clash.

Edge cases

• The candidate was rescheduled, the panel was substituted or a timezone changed after the failing run started. Refresh the candidate state and reapply the fix against the current values, not the values from the failed run.
• The single candidate proof passes but the full rerun still fails on other candidates. Treat each remaining failure as its own scope, because a shared automation can hide more than one cause.
• The source systems disagree on the correct value. The ATS candidate record governs stage and panel assignment, the interviewer calendars govern availability, and the booked calendar event governs the interview time; record which source won and why.

Compatibility: Calendly at current versions, plus the ATS, calendar or video platform the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zn6FUh8H91nXFlRT8TA-cA

Resolved from the public thread: https://vectle.com/posts/pst_zn6FUh8H91nXFlRT8TA-cA

Thread query: how to fix Calendly panel interview error organizer double booked same room fails error

TL;DR: Fix this in Calendly by acting on the exact problem first: add the interview room as a calendar resource with conflict checking turned on in Calendly, remove the second panel that holds the same room at the same time, reassign that panel to a free room of the right size, and confirm both panels now show different rooms. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Fix this in Calendly by acting on the exact problem first: in Calendly open the panel event, delete the duplicate room booking so only one room reservation remains for the panel, check the organizer calendar for the overlapping event that caused the clash, and move the panel or the room so each booking has its own room and time. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.

Calendly panel interview error organizer double booked same room

Use this when

• The operation in Calendly fails with this exact problem: Calendly panel interview error organizer double booked same room.
• The same failure repeats on retry with unchanged inputs.
• An interview, a panel booking or a candidate confirmation is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The interview completes and you only disagree with a hiring decision such as advancing a candidate. That is a hiring call, not this failure.

Steps

1. Reproduce the failure on one named candidate in Calendly and record the full problem text plus the candidate, requisition or panel involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Calendly open the panel event, delete the duplicate room booking so only one room reservation remains for the panel, check the organizer calendar for the overlapping event that caused the clash, and move the panel or the room so each booking has its own room and time. Verify: the single failing candidate now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring candidates, panels or requisitions that share the same automation, template or calendar sync, because this class of failure rarely affects only one candidate. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Calendly on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the ATS candidate record, the interviewer calendars or the booked calendar event, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the candidate record so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Calendly panel interview error organizer double booked same room

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single candidate proof, then the full rerun.

How to fix - Calendly panel interview error organizer double booked same room

The how to phrasing for the same failure in Calendly. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Calendly troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Calendly checks the organizer calendar for conflicts but treats a room added as a location as free text, so the same room can be booked twice unless the room is a checked resource and the duplicate reservation is removed.

Edge cases

• The candidate was rescheduled, the panel was substituted or a timezone changed after the failing run started. Refresh the candidate state and reapply the fix against the current values, not the values from the failed run.
• The single candidate proof passes but the full rerun still fails on other candidates. Treat each remaining failure as its own scope, because a shared automation can hide more than one cause.
• The source systems disagree on the correct value. The ATS candidate record governs stage and panel assignment, the interviewer calendars govern availability, and the booked calendar event governs the interview time; record which source won and why.

Compatibility: Calendly at current versions, plus the ATS, calendar or video platform the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstIIOKrht9OyPJ6tFmtyDcQ

Resolved from the public thread: https://vectle.com/posts/pstIIOKrht9OyPJ6tFmtyDcQ

Thread query: Calendly panel interview error organizer double booked same room

TL;DR: Fix this in Calendly by acting on the exact problem first: in Calendly open the panel event, delete the duplicate room booking so only one room reservation remains for the panel, check the organizer calendar for the overlapping event that caused the clash, and move the panel or the room so each booking has its own room and time. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.