Subject: Critical Timezone Bug – All events shifted by -2 hours (Google Calendar + Manual input) Hello Bases44 Support Team, I need your direct technical assistance with a critical bug that is breaking my entire scheduling system. Every time I create or import an event (either manually or from Google Calendar), the time is shifted 2 hours earlier. For example: If I enter 08:00, it appears in the system as 06:00 If Google Calendar has an event at 10:00, it appears as 08:00 in your calendar This happens consistently and makes the system unusable for real scheduling. What I already tried I have already: Set my location and timezone to Jerusalem / Asia-Jerusalem Verified the timezone in my Google Calendar Reconnected Google Calendar Tested manual event creation inside Bases44 Tried different browsers and sessions None of this fixed the problem. So this is clearly not a user-side configuration issue — it is a backend timezone conversion bug. What this likely means technically This looks like a classic UTC / local timezone double-conversion bug: Times are probably being: Converted to UTC And then incorrectly treated again as local time Or the timeZone field from Google Calendar events is being ignored. Why this must be fixed by your team I cannot continue testing or “trying settings” because: This is a system-level bug It affects every event It corrupts real patient scheduling I also do not want to spend any more credits trying to work around something that is not under my control. What I need from you I need your engineering team to: Inspect the Google Calendar sync Inspect how manual dates are stored Ensure all times are handled correctly for Asia/Jerusalem And stop the -2 hour shift This must be fixed at the platform level. Please escalate this to your technical team. Thank you, Yoni