I am facing slowness in the App and on checking the Audit Logs there are errors from Appsheet Database.
Following is one of the errors -
“Errors”: “Unable to delete row from table ‘Job List’. → Error: Data table ‘Job Task Log’ is not accessible due to: An error occurred while fetching rows from AppSheet database.”,
“Exception”: "LegacyDataLayer.Exceptions.CustomerFacingExceptionWithCode: Error: Data table ‘Job Task Log’ is not accessible due to: An error occurred while fetching rows from AppSheet database.
Other errors are also similar but from different tables. I could not find any documentation or post regarding this issue.
If anyone has faced similar issue in the past, kindly share your knowledge.
!’ve checked our system records and haven’t seen other reports matching this behavior, nor have I been able to replicate it on my end. It may have been a temporary backend sync delay.
Could you confirm if you are still seeing the deleted app or receiving those automated emails?
I’m having issues with Smartsheet as a data source; I’m getting this message:
Error in SmartsheetProvider retry:
Object reference not set to an instance of a object
I’ve already contacted the support team, and they say they are still investigating.
I’m mentioning this in case there was an internal update, to see if it might be related.
@Jose_Arteaga, the issue is still being faced by the team members and it is impacting the operations.
The AppSheet Support access is already enabled. Kindly let me know when we can expect an action from the Appsheet team.
Also, please let me know if there is any other way to get in touch with the Appsheet Team to debug the issue, any mail thread or specific ticket I can track for my issue.
This issue has been observed for the third time in the last 4 months. When it happened couple of months back, I had connected with an Agent over Google Chat but the Agent couldn’t find the root cause and after sometime the issue was not seen. The same has happened whenever we see the issue, it persists for some hours after that it works properly.
Resolving This issue is a top priority for our Operations to run smoothly. Kindly check if there is an ETA on the ticket and if its possible to connect with the Agent over a Google Meet to find the root cause.
I appreciate your support through the process and hoping to find the root cause at the earliest.
Since the issue is intermittent, there is no immediate way to confirm whether the issue was resolved for my application. We would have to wait and observe. However, I really appreciate that the issue was being worked on proactively.
As you have pointed out that the issue was part of a larger issued raised in the thread you shared, for tracking purposes Is there any public documentation for the ticket and its RCA. This helps us in staying updated on any further developments.
The metrics showed some initial improvement following yesterday’s adjustments, performance hasn’t fully recovered across all apps yet.
The engineering team continues to investigate to identify remaining bottlenecks and ensure a complete fix.I’ll keep you posted as soon as I have more news from the team!
