Hei all!
Today (19.06.2025) and yesterday, our AppSheet app started experiencing sync errors - based on the AppSheet Performance Analyzer, some API calls take 20 seconds and then fail. And then the next ones complete in 0.5-2 seconds successfully.
Our AppSheet app is backed by a SQL server running in Google Cloud, but I do not see any issues there - the CPU, memory, and read/write look within optimal limits.
Is anyone else experiencing Intermittent sync errors these past days?
Hi,
We also have some application that is backed by SQL Server from Azure, and we experience intermittent connection to the SQL Server for the past few days also.
This is our Error message
"Error: Data table is not accessible due to: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 35 - An internal exception was caught)."
Admins please help.
Status update
It seems to be better today, no failures yet.
From last week to this week, the app has been intermittently slow. Synchronization delays are obvious. Also, adding and updating data can take a surprisingly long time.
We have received information that this phenomenon does not occur all day, but at certain times of the day. It seems that the operation becomes particularly slow around 5:00 PM Japan time. In UTC, it is around 8:00 AM.
The frequent server downs that occurred until last month have disappeared, but the delays in synchronization and data processing are just as serious as the server downs. This defect is causing automations that are not executed, which is disrupting business operations.
Same problem from Vietnam.
Please check and resolve it asap.
Thanks
Same in South Africa, all my client PDF automation bots are timing out, they spiked from 45 seconds successful to all 120 second timeouts consistently.
Please contact AppSheet Support for help with this.
Hello,
Thanks for bringing this to our attention. We did have an increase some sync request latencies late last week, specifically originating from APAC, due to higher volume than usual. We've looked at some scaling factors and made some adjustments and are back to baselines at peak volume. We're taking some additional steps over the next few days as well to prevent reoccurrence of long tail latency increases
Hi, @Adam_Stevens
Thank you for the prompt response and for investigating the sync latency issues.
However, I would like to respectfully reiterate our request regarding incident communication. While we're grateful for the resolution, incidents like this sync delay should ideally be communicated through the Google Workspace Status Dashboard in real-time.
Even though this may not have been classified as a "major outage," the prolonged sync delays significantly affected our daily operations, Bot executions, and overall workflow efficiency.
Could you please consider updating the incident reporting criteria to include performance degradations like sync latencies on the Google Workspace Status Dashboard?
Thank you again for your attention to this matter and for the technical resolution.
User | Count |
---|---|
17 | |
7 | |
6 | |
5 | |
3 |