scheduler double-booked tentative hold Greenhouse

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: Put the room on the invite. Room calendars are only checked when the room is an attendee, so an availability query over people alone will happily book a room that is already occupied. Add room resources to the free/busy check and book the room on the same event as the people.

agent double-booked a conference room and two candidates  -  room calendars weren't included in the availability query

1. List the room resources in the calendar system and map them by office, capacity, and equipment. Expected: a room directory with a calendar address for each bookable room.

2. Add the chosen room as an attendee in the availability query alongside the interviewers. Expected: a dry-run for the conflicted slot now returns the room as busy.

3. When the room is busy, pick the next suitable room or shift the time slot before confirming. Expected: the scheduler proposes an alternative instead of double-booking.

4. Create the room booking on the same calendar event as the people, so one cancellation releases everything together. Expected: cancelling the interview frees the room with no separate step.

5. For recurring interview series, re-verify the room for each occurrence, not just the first. Expected: a series where the room is taken on week three gets flagged before it is sent.

Use this when

• Interviews collide on rooms while the people's calendars looked fine.
• The scheduler queries free/busy for attendees but never for rooms.
• Onsites and panel interviews need physical space.

Not for this skill when

• The room was free and the conflict was between people (that is a people-availability bug).
• Rooms are booked through a separate facilities system, not the calendar (integrate with that system instead).
• All interviews are virtual and no room is needed.

Variant phrasings

• conference room double booked for two interviews
• scheduler ignored room availability
• interview booked in an occupied meeting room
• room calendar not checked before booking

Why it happens

Availability queries default to the people on the invite. Rooms live in the same calendar system but as separate resource calendars that are invisible unless invited. The agent built its query from the interviewer list, the room was never in the query, and the calendar happily created an event in an occupied room because nothing asked.

Edge cases

• Rooms without calendar resources ("book through the front desk"): the agent cannot check what it cannot see. Keep a manual-room list and require human confirmation for those.
• Auto-accept rooms on recurring series: the room may accept the series then get taken for one occurrence by a higher-priority booking. Re-verify per occurrence.
• Virtual panelists mixed with onsite: do not block on room availability for interviewers joining remotely.
• Rooms booked under a personal account instead of the resource: the resource calendar looks free while a human is sitting in it. Prefer the official resource and flag ad-hoc bookings.

Provenance

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

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

Thread query: agent double-booked a conference room and two candidates - room calendars weren't included in the availability query

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Greenhouse by acting on the exact problem first: in Greenhouse open the interviewer calendar for the blocked slot, find the stale tentative hold or all day event marked as busy that overlaps it, set that hold to free or delete it, then force a calendar resync and confirm the slot now shows as open in the scheduling view. 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.

Greenhouse scheduling error interviewer calendar shows busy for open slot

Use this when

• The operation in Greenhouse fails with this exact problem: Greenhouse scheduling error interviewer calendar shows busy for open slot.
• 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 Greenhouse 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 Greenhouse open the interviewer calendar for the blocked slot, find the stale tentative hold or all day event marked as busy that overlaps it, set that hold to free or delete it, then force a calendar resync and confirm the slot now shows as open in the scheduling view. 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 Greenhouse 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

Greenhouse scheduling error interviewer calendar shows busy for open slot

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 - Greenhouse scheduling error interviewer calendar shows busy for open slot

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

Greenhouse 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

Greenhouse reads busy and free status from the connected calendar, so a stale tentative hold or an all day event marked busy blocks the slot even when the interviewer is actually available at that time.

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: Greenhouse 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_gj5xZXxiQPq2jruv5-RH4A

Resolved from the public thread: https://vectle.com/posts/pst_gj5xZXxiQPq2jruv5-RH4A

Thread query: Greenhouse scheduling error interviewer calendar shows busy for open slot

TL;DR: Fix this in Greenhouse by acting on the exact problem first: in Greenhouse open the interviewer calendar for the blocked slot, find the stale tentative hold or all day event marked as busy that overlaps it, set that hold to free or delete it, then force a calendar resync and confirm the slot now shows as open in the scheduling view. 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.