[Bug]: Autoscheduler intermittently fails save/swap with “room is already occupied”

[workonlly]

Description

The autoscheduler has an intermittent save/swap failure that can reject valid changes with a “the room is already occupied” error. The repository already documents this as an unknown bug in autoscheduler/TODO, but the issue remains unresolved and visible in normal scheduler use.

Steps to Reproduce

1)Open the autoscheduler for a program with scheduled sections.
2)Attempt to save a schedule change, especially a swap.
3)Repeat the operation a few times or try different swaps.
4)Eventually, the save can fail with a “the room is already occupied” message.

Expected Behavior

Saving a valid schedule change should succeed unless there is a real conflict. Swaps should not fail intermittently for the same underlying state

Actual Behavior

Saving or swapping sometimes fails with an incorrect “the room is already occupied” error, even when the failure is not consistently reproducible.

Screenshots

No response

Operating System

No response

Browser

No response

Additional Context

No response

[github-actions]

👋 Thanks for opening this issue!

To keep the tracker focused, new issues are locked for conversation until a maintainer has reviewed them. This helps us avoid duplicates and ensure issues are actionable.

What happens next:

• A maintainer will review this issue shortly.
• If approved, the conversation will be unlocked and the needs-triage label removed.
• If this is a duplicate or out of scope, a maintainer will close it with an explanation.

Please don't worry — your issue hasn't been rejected, it's just waiting for review. 🙏

[mn3m-24]

/assign

[github-actions]

✅ @mn3m-24 has been assigned to this issue. You have 4/5 issue(s) assigned.

📖 Getting Started · Contribution Rules · Code of Conduct

[workonlly]

can you provide the roadmap how you will solve the issue so that if i can help i can suggest something