For Support

What the bug looked like to a user

A user switches their working branch (via the branch selector) to one they haven't visited yet this session, then immediately — within roughly a second — does one of:

• Opens Create New Appointment and the form is present (the crash could

happen just from the form rendering, not from clicking anything).

• Clicks the small calendar icon next to the Day field (month view).
• Turns on Repeat and clicks Available Slots.

The app would go to a blank/broken screen (an uncaught JavaScript error — not a friendly error message, not a toast, just a broken page) instead of showing the form or modal. Reloading the page or waiting a moment and retrying would work fine, because by then the branch's data had finished loading and gotten cached.

What to ask a user reporting "the calendar/appointment screen went

blank"

1. Did you just switch branches? This is the single most useful

question — the bug only manifests in the few hundred milliseconds to a couple of seconds after switching to a branch not already loaded this session.

1. **Does it happen again if you reload and immediately retry the same

steps?** If yes and consistently reproducible regardless of timing, this is probably a different issue — escalate as a new bug rather than assuming it's this one.

1. Which browser tab/screen were they on — Create New Appointment

form, the month-view picker, or the repeat-appointment "Available Slots" flow? All three were affected, but knowing which helps narrow down if a regression is in the same area or something new.

What to tell them

This was a known timing bug, fixed pre-release — it should no longer occur in versions containing this fix. If a user reports the same symptom (branch switch → blank screen) after this fix has shipped, that's not expected and should be escalated as a new issue, not assumed to be this one recurring.

What "fixed" looks like now

Instead of crashing, the same sequence (switch branch → immediately open one of the three screens) should show the screen with a brief loading / default state, then update to the real data once it arrives — no blank screen, no reload required. See the walkthrough for what each of those screens looks like once working.