Codility panel scheduling conflict error same interviewer booked twice

TL;DR

Fix this in Codility by acting on the exact problem first: in Codility open both panel sessions for the doubled interviewer, keep the earlier confirmed session, reassign the second session to a trained backup interviewer with the same skills, notify both interviewers, and turn on the overlap check for panel creation. 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.

Codility panel scheduling conflict error same interviewer booked twice

Use this when

• The operation in Codility fails with this exact problem: Codility panel scheduling conflict error same interviewer booked twice.
• 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 Codility 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 Codility open both panel sessions for the doubled interviewer, keep the earlier confirmed session, reassign the second session to a trained backup interviewer with the same skills, notify both interviewers, and turn on the overlap check for panel creation. 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 Codility 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

Codility panel scheduling conflict error same interviewer booked twice

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 - Codility panel scheduling conflict error same interviewer booked twice

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

Codility 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

Panel creation checked each session on its own without a cross session overlap check for the interviewer, so two coordinators could book the same person at the same time until one session is reassigned.

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: Codility 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_DF3pStsuXRnrUKb1XrMlkg