Time on Upcoming Bookings screen does not match time of the booking or on the calendar.

[trippjax2]

The time within the booking, booking confirmation email, and calendar entry are all correct, in my case US Eastern Time. However, the Upcoming Bookings dashboard shows a different time regardless of location type. The profile settings are set to US Eastern. The .env TZ is set to America/New_York. However, the server logs (server) is set to UTC time. Please advise what I need to do to get the booking screen to reflect local time.

[dosubot[bot]]

The Upcoming Bookings dashboard gets booking times from the backend (usually in UTC), but the frontend is responsible for converting and displaying these times in your local timezone. The correct timezone is usually determined by your profile settings, but if those aren't respected, the frontend may fall back to your browser's timezone or even UTC. The .env TZ and server log timezone settings do not affect what you see in the dashboard—they only impact server-side processing and logs.

If your profile is set to US Eastern and other parts of Cal.com (like emails and calendar entries) show the correct time, but the dashboard does not, this suggests the dashboard's frontend is not consistently using your profile's timezone for display. This could be due to a bug or a missing timezone context in the React components that render the bookings table. The codebase uses Day.js with timezone plugins for formatting, and there are hooks/utilities (like useProfile or useViewerTimeZone) that should ensure the correct timezone is applied, but there may be inconsistencies in how these are used in the dashboard components. The frontend should always convert UTC times to your profile's timezone before displaying them, but if it doesn't, you'll see the wrong time (often UTC) in the dashboard.

There isn't a user-facing configuration to force the dashboard to use your profile timezone if it's not already doing so. If you're self-hosting, double-check that your user profile's timezone is set correctly and that your browser's timezone matches your expectations. If the problem persists, it's likely a frontend bug where the dashboard isn't applying the profile timezone as intended, and it may require a code fix to ensure the correct timezone is always used for display.

References:

• Timezone handling in Day.js and frontend display
• Recent timezone-related fixes and utilities
• Timezone normalization and profile settings context

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}