Data table is not accessible due to: An error occurred while fetching rows

[PaulK721]

Hi All, I have  an appsheet database with 9 tables most of which have less than 500 rows but the App is consistently failing sync as a result of the above error on a table that doesn't have any views in the App. The table is purely to hold archive data copied then deleted from another table so I as the app creator can use it for statistics (order history etc). I have plenty of successful syncs throughout the day, but then there will be a string of unsuccessful syncs for no apparent reason, all failing as a result of this same table. The error is as below:

Operation: App sync

Message: Error: Data table 'Sheet1 Archived Orders' is not accessible due to: An error occurred while fetching rows from AppSheet database.

The audit log doesn't show anything of use, does anyone have some suggestions of things I should check? Thanks, Paul

[AleksiAlkio · Accepted solution]

Please contact support. Devs need to debug the reason.

[MTKPA]

This is the second post I've come across with this issue in less than a few weeks--with a reply to the other one. That's four total users having the same problem.

Dev support is saying it's something on my end. I haven't touched that table or any reference to it. I find it hard to believe multiple people are faced with this problem without ever touching their database/table. My externally connected tables work fine, only my internal AppSheet one. 

@AleksiAlkio why would devs debugging at each source be the solution? It sounds like a bigger problem with the API or AppSheet code updates. Have you heard anything on this or when to expect a global fix?

[bscameheorn]

We are also experiencing the same issues. I did notice that Google alerts you when entering appsheet that any links to drive from your app need to be updated before May 1st. I do not know if that has any bearing on the issue.

[bscameheorn]

We are also having this issue since Friday where appsheet is throwing an error "Unable to fetch app definition Error:Error: Data table "<table_name>" is not accessible due to: An error pccured while fetching rows from AppSheet database. This was working fine before Friday and no changes were made whatsoever on our end.

[AleksiAlkio]

Because it probably has something specific with your app setup. If this would be a generic issue, we could see more than few posts in here.

[niklash]

We are facing the same problem since today. We haven't touched any of the affected tables. Also only internal tables are affected.

Is there any solution so far?

[MTKPA]

@AleksiAlkio Multiple users on multiple posts having the same problem in a very short window. This tells me it's an issue on the AppSheet side, especially because there are no historical posts with this specific problem. 

@niklash Google dev support elevated it to their "specialists". I got a reply this morning that it has been fixed and stated the following: 

"It was a backend issue and multiple users were facing the same issue. It is now resolved for everyone, no changes were needed at your end."

If you still have issues, reach out to dev support and reference this post. 

[niklash]

@MTKPA Thanks for your response!

The issue is also gone for us without any action on our side

[AleksiAlkio]

Did it solve your challenge as well?

[Eosvill]

Estoy aun experimentando el mismo error, como lo puedo solucionar?

[PaulK721]

This solved my issue also.

[Duane_Pruuel]

Been having this issue for two weeks now and they keep saying a "Specialist" is looking into it.  Typical Blow off emails.  The app works fine but it will not let me regenerate or add new tables.  Spent 4 hours on chat tech support this morning and we accomplished absolutely nothing.

[T_I_Phong]

I have encountered this issue many times and it has been happening for a while. I have previously contacted support, but the explanation given was that the error would resolve itself. I noticed that the issue often arises when a shared database is used for multiple apps.

When encountering the error, I typically handle it in two ways:

1) Regenerate Schema

2) Set False in the Security Filters until the connection can be reestablished, usually within a few minutes.

[Duane_Pruuel]

Have done that multiple times.

--
Thanks,

D