## TL;DR
Fix this in loop scheduling by acting on the exact problem first: open the load count for the flagged interviewer, check whether shadowing sessions and debriefs are being counted as full interviews, correct the load counting rule if they are, and rerun the loop build to see whether the panel now fits without moving anyone. 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.

```text
loop scheduling error final round panel exceeds interviewer load limit
```

## Use this when
- The operation in loop scheduling fails with this exact problem: loop scheduling error final round panel exceeds interviewer load limit.
- 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 loop scheduling 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: open the load count for the flagged interviewer, check whether shadowing sessions and debriefs are being counted as full interviews, correct the load counting rule if they are, and rerun the loop build to see whether the panel now fits without moving anyone. 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 loop scheduling 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

### loop scheduling error final round panel exceeds interviewer load limit
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 loop scheduling error final round panel exceeds interviewer load limit fails error
The how to phrasing for the same failure in loop scheduling. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### loop scheduling 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
Load limits count what the counting rule tells them to count, and counting shadows and debriefs as full interviews inflates the load until an interviewer appears over limit while their real interview count is within it.

## 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: loop scheduling 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_rYb7W8uPfPS4m-wMUqgJ0A