Have sent this into the appsheet support / help centre but, I thought it wouldn’t hurt to put it here.
I’ve been using the system for a good period of time now haven’t really had many issues but as of yesterday I’ve had one application just fail to sync completely.
The main two errors I see are:
Error: Data table ‘STW Entry’ is not accessible due to: The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing..
The second error then states that it cannot read one of the tables
Spreadsheet data for ‘FlowAppSTWPAM-*******:1.000706:STW PAM Installation Handler’ could not be read
I haven’t changed anything over night, it just appears for any process that is taking longer than 30 seconds to sync it just crashes, my other applications are working fine but there sync times are between 10 - 15 seconds.
I have tried to create a copy of the failing application to work on it to resolve the issue but, it refuses to process any of my changes just gets stuck loading.
Worse comes to worse I’m going to try rebuilding the application from scratch this evening was just wondering if anyone else has had anything similar.
My teams out in the field have still managed to submit forms & view the latest ‘cached’ version of there application but, they can’t manually sync due to the above errors.
AppSheet as a whole is having a lot of problems lately, especially on the backend, so your problem could be related. Unfortunately, AppSheet staff have been silent on the issue.
You cite two errors. If they are occurring together, assume the second is a result of the first and work to solve the first one first.
What is your app doing when it experiences the timeout? Please post screenshots of the related configuration.
Yes I’d assume the errors are cupelled together, the timeouts come from any sync process (manual or automated) that doesn’t involve an action taking place like a form being submitted & is over a time threshold of 30 seconds to sync. The error claims it cannot read the table below, which hasn’t changed name or configuration.
Apologies Steve never had to do one of these before so I don’t know exactly what information you’d require to investigate further. I’ve tried resetting source path & that didn’t have any effect on it.
I’ve got other applications that are working fine for the majority of time & only have the odd error when the sync passes the 30 second barrier.
The error referencing HttpClient is odd–I don’t recall seeing it before. I’d guess a change has been made to the backend by the AppSheet developers. Perhaps they added a new timeout? Maybe they’re reimplementing the Google Sheets connector? There’s no way to know. If this is the case, going through Support is your only option.
Does your spreadsheet use formulas? If so, they’re recalculated as part of every sync. That recalc time would count against any timeouts AppSheet imposes.
Yeah I will see what support says, yes I do have some formulas in this table & a couple of others connected to this application, we went through some development with the other two applications I run to remove formulas from it once I learnt about Bots & Apps Scripts, this was the last project that needed doing. The catch problem with this one is that to make those changes go through I need some form of sync to happen which is being stopped by this HttpClient issue, thanks for looking into Steve I will persist on with the Appsheet support team.
Yeah I’ve also been getting the Http timeout error this past week. It seems to appear for 30 minutes in the morning around 9am PST. Then it resolves itself until it reappears the next day.
It’s affected all of our apps as the error states it’s an issue with the google sheet.
This issue started appearing around the same time as the 429 status code issue, and it persists after the fix went in to resolve the 429 issue. I’ve reached out to support a couple times and they’re presumably investigating. Hope this gets resolved soon.
I’m also encountering the same issue and your post really resonated with me. Just like you, my app had been working fine for quite a while and then suddenly started failing to sync without me changing anything on my side. I’ve seen the same timeout error where the request exceeds 30 seconds and then it throws the table-read error afterward. It seems to only affect apps that require a bit more processing or larger datasets, while lighter apps are still syncing within 10–15 seconds without problems.
I also tried duplicating the app to troubleshoot, but the copy wouldn’t load properly and kept hanging, so I completely understand your frustration there. At the moment, my team can also still use the cached version but can’t manually sync, which is becoming a big challenge for fieldwork. From what I’ve observed, it might be related to a recent change or limitation on AppSheet’s side rather than something we configured, but I’m still digging.
If you happen to find a solid workaround or solution before I do, please share here — and I’ll do the same. It’s reassuring to know someone else is running into the same problem and we might figure it out together.
I’m running into the exact same issue and your post really hit home, especially since my app was working perfectly until recently, with no changes on my end. Syncs now time out past 30 seconds, especially on apps with larger datasets, while simpler ones are fine. If you find a workaround before I do, please share, I’ll definitely do the same. It’s comforting to know I’m not alone in this.
Request your help in this. There are few posts being added by different app creators to this post thread citing the same issue in last couple of days. So maybe you wish to take a look at it and take it up with a suitable developer team.
Thanks, yes, we received several reports of this last week through the customer support channel and have identified the source of the problem. A fix is already in the release pipeline, but let me see if I can do anything to accelerate that.
Do these fixes get posted in the Release notes of any update, I noticed no mention of this http client timeout error one in any of @lizlynch release notes although we have got community posts from staff members that things should be resolved.
