This error is commonly seen because of app configuration that is not an internal error. In such cases, it means you have two virtual columns that reference each other. Because each is waiting for the other to compute its value, neither ever completes. Such conditions can be very tricky to track down.
This is likely just fallout from the first problem: fix the first and this one will likely disappear.
I agree with Steve. There could be a few tables in your app where a substantial cross referencing could be taking place in the virtual columns expressions.
I had an opportunity to work on a similar issue last year end.
The solution will depend on app business functionality. I had solved the issue by making those interdependent virtual columns to compute only on demand by the user. This avoids long sync cycles on every sync by every user.
Ok. Thanks a lot for for hints. We will defenetly look into this. But this also seems strange.
The reason I wonder is that this error occurs frequently on six different apps. And we have not done any simelar or significant changes to these apps. Some of them are quite different from others. Not much data either. None of the apps had any sync issues 1 month back. They all synced on 1 - 5 seconds. They still do, when they sync. But quite often they âhang upâ or âtime outâ.
If it was a cross referance in a viritual column this sholdt always fail, or am I wrong? And very strange that all different apps suddenly has this error this frequently?
Thanks Steve. All suggestions here are appreatiated!!
Just some additional info:
Same error occurs in 6 different apps, but randomly. Sometimes it adds, deletes, sync normally in 1-5 sec. Other times we get timeout/hangup in form of these different errors.
The different errors seems not app related. Not user related. Not related to amount of data.
All apps synced without these issues approx one month ago, and we have not done any updates.
The apps are quite different of each other.
We use MS SQL server on Google Cloud for all these apps.
When saving eg. six simelar data changes, four could go through fine in a flash, and then fail in a timeout or another error on the fifth. Trying to sync again will not work. But if we do nothing and try to sync maybe 30 minutes later again, it might suddenly go throughâŚ
Do you still think it is a cross referance in all these apps? Maybe due to an update from appsheet suddenly not allowing it anymore? Im lost of ideas hereâŚ
Than you!!
Please look in thread below for furher hints and additional info if this could be of any help to the technichians.
It is odd that several apps were affected around the same time. Perhaps all affected apps used a similar design pattern that made use of a common table, and that common table received some new data that triggered the problem behavior in all of the apps that used the table?
And, of course, itâs possible the developers made a change that caused this. But Iâm inclined to call that unlikely.
My suggestion:
FALSE. Donât just remove the expression, replace it.Nothing new there.
Thanks again! We will defenetly do that. And the re create the sec filters one by one.
Two or maybe three of the apps are a bit simelar, being copied 3 years ago and developed further after that. The others are totally different, but of course with the some of same app developers involved.
The errors with âTimed out waiting for a resourceâ refere to different tables every time. And errors also occur when adding or editing data. Not just syncing. So errors occur before data âhitsâ the sec filtersâŚ
I must say I think this is something else, but in loss of other ideas Im willing to try anything!!
Below is two different errors from edit row from two different apps (2 minutes apart):
True, but just showing several different apps with the different errors. Suddenly (approx 1-2 month ago) all our apps get all the same variation of error messages and frequentlt fail in both adds, edits, deletes and syncs.
@Shourya_Tomar Are there any news?
We cannot see that any egeneers have entered any of our apps lately? Last time was 25th of june. Are they working on this?
Here is an email we received for one of our customers today:
Now we are starting to get seriously worried about the BYGGLE system.
One thing is that errors can occur, but that it will take so long to fix is ââworrying, when we look further down the road.
We like the system, but right now we are terrified that we are about to lose control of everything!
My Team and I have had a long chat today, and what we have come to is.
BYGGLE seems like a good platform to work on, and we want to continue with it, but if this is not in order when we return from vacation on 27.07.2026 we will have to turn around and look at other solutions.
We are completely dependent on working faster and more smoothly. Now it is unfortunately just frustration.
Hope you find a solution to the problem soon! I am available all the time.
Any progress, @Shourya_Tomar?
Same here, all of our apps are blocked, running extremly slow and canât sync.
Error about time out, however the app is light or heavy running.