Need Help with time out large/slow loading table error

AppSheet AppSheet Q&A
1

i am getting this error sometimes, like not always like 1 out of 10 time of sync problem and every time error is for different table ,
everytime a different table gets time out and error is "
Error: Data table ‘table name’ is not accessible due to: Timed out waiting for a resource. The reason is usually a very large/slow loading table or a cross-table cycle in AppSheet formulas..

and ealier there was no this error
this error is coming from last 3 days only, which is creating a lot of problem for my employees
i had made all related rows formula {} wherever i used ref to decrease time taken but still error continues,
i can’t even say that, data has grewed from last 3 days, it same

can anyone help me to get rid of this

2

I have noticed these errors also intermittently occurring again, it feels like it happens on cold start for my client, when they all sync in mornings and the sheets API cannot handle so many requests to the same sheet..

@Jose_Arteaga Please ask tram to verify what rate limits may apply when many users sync the same Google sheet…

3

i am using the postgres , in the cloud logs , it just says that user appsheet cancelled the request

@Jose_Arteaga can u pls help me in this

4

Thanks @Denzil_Snyman!

Hello @RISHAV_JINDAL,

Welcome to the AppSheet community!

Indeed, this error happens when the data table takes too long to load due to either a slow server, a very large dataset, or complex calculations.

As stated here, there’s an option to look at which table is taking long to load and perhaps optimize whatever is needed.

Please let us know of any findings.

5

but my concern was that i haven’t added any new calculations or columns and dataset is also same
it was working perfectly fine from last 5 months ,
suddenly errors started from last few days

6

Any change on the DB maybe?

7

Does your app get a lot of use? Many users in a short span of time? Many data changes? Large bursts of activity could account for the intermittent behavior.

Does your app have many tables? Say, more than 20? A complex web of data sources, especially across data hosts (multiple spreadsheets, calendars, SQL servers, etc.) introduces a lot of variables that must all work correctly to avoid problems. A weak link anywhere in that web can cause a problem, and may be intermittent.

Can you characterize the complexity of your app, and the nature of its use profile?

8

no thats havn’t happened from past one month, thats why i am concern about this error

9

Yes tables are there about 12-13 ,others small and 3-4 big with 6000 of rows,

but i have two modules of appsheet(not linked with each other) but using same tables, others are using more tables than the specific module
but error is occuring only this one module, others are working great with same amout of data, more complexity and tables

10

Thanks Steve,

My recommendation at this point is to reach out to the support team so that they can further analyze this issue. Please follow the steps below:

  1. Go to Appsheet help

  2. Scroll down to the bottom, you will find a box with the following text

    Need more help?

    Try these next steps:

    Contact us
    Tell us more and we’ll help you get there

  3. At this point you will be redirected to a three steps process in which users will possibly find answers to the query they have. Click Next

  4. Click Next Step

  5. Specify your preferred language and either click on Chat or e-mail

Let us know how that goes please.

11

I wouldn’t call that a lot. All are in Postgres? Any spreadsheets? Any AppSheet Database?

Of course, the most common cause of this error is exactly what it says: a cross-table cycle. A cross-table cycle happens when two tables refer to each other. An update in one table prompts an update in a second table, but the second table needs data from the first that is in the process of being updated and is waiting on the second! These can be tough to find and tough to fix. They can also be intermittent, because they can be tied to specific values in specific columns of specific rows: only the right combination of row, column, and value might trigger it!

12

One in Google sheets and other all in postgres on Google cloud

13

I wouldn’t expect a problem with that.

I encourage you to focus on your virtual column expressions, specifically those that reference other tables explicitly (with the likes of LOOKUP(), SELECT(), FILTER(), etc.) or using derferences.