Resolved -
We deeply appreciate your patience as our team worked diligently to resolve the recent calendar event synchronization timing issue. We are pleased to inform you that we have successfully identified the root cause of the problem and have implemented a fix to resolve it.
Our team is committed to ensuring normal calendar performance and will continue to monitor this issue closely to ensure the best possible customer experience. For any further questions and concerns, please reach out to our dedicated support team. Thank you.
Apr 29, 10:23 MDT
Monitoring -
We appreciate your patience as our team is working diligently to resolve the issue with unpredictable timing of calendar event synchronization. We have identified an issue that was causing these symptoms, and have developed and implemented a fix to resolve the issue.
Our team is dedicated to ensuring normal calendar sync performance, and we will continue to monitor the issue to ensure full resolution and provide additional status updates if needed. Thank you.
Apr 22, 11:08 MDT
Identified -
We appreciate your patience as our team is working diligently to resolve the issue with unpredictable timing of calendar event synchronization. We have identified a potential issue which could be causing these symptoms and are actively working to address it.
Currently, we have observed that the PgBouncer and PgBouncer_ro services will not run simultaneously on job managers. Due to the startup script, it is unclear which of the two services is running, and it seems that the "last to start wins" scenario occurs. In the event of an instance restart, a different service could potentially "win" and cause further inconsistency.
To resolve this, we have worked on a solution where these services now have separate unix socket directories. By providing different unix socket directories to both services, they can run simultaneously and eliminate the inconsistency. This eliminated significant errors on jobmanagers.
Our team is dedicated to restoring normal calendar sync performance, and we will keep you updated with additional status updates as we continue to monitor and make progress towards a resolution.
Apr 19, 11:52 MDT
Update -
Our team is currently working to resolve an issue that is impacting sync times for customers using Google calendars. We want to assure you that our team is fully committed to resolving this issue as swiftly as possible.
We recognize the importance of timely event syncing, and we apologize for any delays you may be experiencing. Restoring normal calendar sync performance is our top priority, and we will keep you updated with additional status updates as we make progress towards a resolution.
Thank you.
Apr 18, 14:34 MDT
Update -
We are continuing to investigate this issue on priority. We apologize for the delay, next update will be shared at 3:30 PM CST.
Apr 18, 10:34 MDT
Investigating -
As the fix implemented haven't resolved the issue completely, we have moved to the investigation phase. Our Engineering team is currently investigating the issue with Google Calendar Service to determine the cause of disruption. The next update will be posted at 11:30 AM CST.
Apr 18, 06:38 MDT
Update -
We are continuing to monitor for any further issues for next 12 hours.
Apr 17, 06:42 MDT
Update -
We are continuing to monitor for any further issues for next 12 hours.
Apr 16, 15:03 MDT
Monitoring -
A fix had been identified and applied to optimize the performance of the Google Calendar Sync. We are moving into the Monitoring Phase for the next 4 hours and next update will be shared at 3 PM CST.
Apr 16, 09:56 MDT
Update -
We are continuing to investigate this issue on priority. We apologize for the delay, next update will be shared at 11 AM CST.
Apr 16, 05:49 MDT
Investigating -
As the fix implemented haven't resolved the issue completely, we have moved to the investigation phase. Our Engineering team is currently investigating the issue with Google Calendar Service to determine the cause of the disruption. The next update will be posted at 7 AM CST.
Apr 16, 02:32 MDT
Update -
We are continuing to monitor for any further issues for next 12 hours.
Apr 15, 06:51 MDT
Update -
We are continuing to monitor for any further issues for next 12 hours.
Apr 14, 13:47 MDT
Monitoring -
A fix has been implemented. We are moving into the Monitoring Phase for the next 12 hours.
Apr 13, 02:12 MDT
Update -
We are continuing to investigate this issue on priority. We apologize for the delay, next update will be at 3 am CST
Apr 12, 22:13 MDT
Identified -
As the previous fix implemented did not resolve the issue completely. We are continuing the investigation with Google Calendar Service and have determined the cause of the disruption and are working on a fix. The next update will be posted at 8 PM CST.
Apr 12, 15:06 MDT
Update -
We are continuing to investigate this issue on priority. We will post another update at 4 PM CST.
Apr 12, 10:27 MDT
Investigating -
As the fix implemented haven't resolved the issue completely, we have moved to the investigation phase. Our Engineering team is currently investigating the issue with Google Calendar Service to determine the cause of the disruption. The next update will be posted at 12 PM CST.
Apr 12, 07:22 MDT
Update -
We are continuing to monitor for any further issues for next 4 hours.
Apr 12, 04:27 MDT
Monitoring -
A fix has been implemented. We are moving into the Monitoring Phase for the next 4 hours.
Apr 11, 23:58 MDT
Identified -
The issue with Google Calendar Service. has been identified and a fix is being implemented. We will post another update at 1am CST.
Apr 11, 19:56 MDT
Update -
We are continuing to investigate this issue in regard to Google Calendar Sync. The next update will be posted at 11:45pm MDT.
Apr 11, 19:35 MDT
Investigating -
We are currently investigating an issue with customers using Google Calendar Service. Our Engineering team is currently investigating to determine the cause of the disruption. The next update will be posted at 7:45pm MDT.
Apr 11, 15:46 MDT