Summary When the "Unified Service Booking View" toggle is enabled in Calendar View > Manage View, confirmed service bookings are rendered with strikethrough text and labelled as "Cancelled." The backend data is correct. This is a UI rendering issue isolated to the Unified Service View. Environment Sub-account type: SaaS Mode (Agency Pro) Calendar type: Services V2 exclusively Locations: 2 (multi-location, single sub-account) Booking volume: ~460+ migrated appointments via API, plus ongoing organic bookings Steps to reproduce Navigate to Calendars > Calendar View. Select the "Services" scheduling type. Open Manage View (top-right). Enable the "Unified Service Booking View" toggle. Navigate to any date with confirmed service bookings (example: April 27, 2026). Observe: confirmed bookings appear with strikethrough styling and display status "Cancelled." Expected behavior: Confirmed bookings should display with normal styling and status "Confirmed." Actual behavior: Confirmed bookings appear crossed out and labelled "Cancelled" in the Unified Service View only. Diagnostic evidence confirming this is a rendering bug We performed extensive validation across multiple endpoints and views. All confirm the bookings are correctly confirmed in the backend: Public API (GET /calendars/events): Returns status: "confirmed" for the affected bookings. Service Bookings API (GET /service-bookings): Returns status: "confirmed". Appointment List View (Calendars > Appointment List): Shows the bookings as "Confirmed," no strikethrough. Calendar View with Unified toggle OFF: Shows the bookings normally, no strikethrough, correct "Confirmed" status. Calendar View with Unified toggle ON: Incorrectly renders the same bookings as cancelled with strikethrough. Additionally, we attempted to force a re-sync via API by issuing PUT requests to update the booking status and payload fields. The backend accepted the updates and returned confirmed status, but the Unified Service View continued to render the appointments as cancelled. This confirms the issue is in the rendering layer, not in the data. Impact Reception staff rely on the Calendar View daily for scheduling. The strikethrough styling causes confusion, as staff cannot distinguish between genuinely cancelled appointments and the false rendering. Multi-location businesses benefit from the Unified View to see all staff and services in one place. This bug effectively makes that feature unreliable. Current workaround: We have instructed staff to either (a) disable the Unified Service Booking View toggle, or (b) use the Appointment List View, which always reflects the correct backend status. Additional context These bookings were migrated via the public API (POST /calendars/events and service bookings endpoints). Both natively created and migrated bookings exhibit the same rendering issue in Unified View. We are aware of a separate, already-reported bug where service colors revert to random in Unified View when filtering by location. The rendering issue described here appears related to the same Unified View rendering pipeline but manifests differently (status misrepresentation rather than color misrepresentation). We are not requesting a data fix, as the data is correct. This is a request to fix the Unified Service View rendering logic so it reads the booking status accurately. Requested action Please investigate the rendering logic of the Unified Service Booking View to ensure it correctly reflects the backend booking status. A patch or hotfix for this rendering layer would resolve the issue without requiring any changes to the underlying data.