Task was cancelled and Timed out waiting for a resource error during using the apps

AppSheet AppSheet Q&A
1

In UK does anybody experiencing Message: Error:

A task was canceled Error? Errors coming through the apps as well as a couple of: Timed out waiting for a resource. The reason is usually a very large/slow loading table or a cross-table cycle in AppSheet formulas.. Timed out waiting for a resource.

This morning everything was fine. All of the sudden some apps started to throw this error. We have an SQL Database +google sheets but I can still access the data, and the tables does not seem to be particulary slow.

2

Yep same error message

3

Same in Poland.

4

Attn @Jose_Arteaga @Shourya_Tomar

5

Same in Greece

6

Hello all,

There is another thread for the same issue:

I have already escalated this and I will be providing updates as soon as I get a response.

I apologize for the inconvenience caused

7

Hello all,

As stated in the other thread, a temporary workaround has been implemented and the engineering team is monitoring metrics.

I will keep you posted as new information arises.

8

Hello all,

I’m not entirely sure I need to post this in two threads but it is better to ensure communication flows so here I go:

The latest notice says that things should be getting back to normal although we might still see some latency issues which should be resolved soon.

Again, I will keep you posted.

9

Again, sharing the latest update:

Hello all,

As of now, the traffic for EU should be normal. As a summary:

  • Complete Loss of Application Access: Users were entirely blocked from accessing deployed applications, encountering “Unable to fetch app definition. Error:A task was canceled” and database inaccessible errors.
  • Broad Scope of Impact: The issue consistently affected all users across multiple accounts and applies to all of their deployed applications.
  • Severe Operational Disruption: Extremely slow sync times and timeout errors prevented the execution of critical workflows on deployed applications.
  • No Available Workarounds: The issue is persistent and consistent, with no documented workarounds to restore access or bypass the sync failures.

As a workaround, traffic was redirected to other regions while a solution was implemented. As of now, everything is back to normal but please let me know otherwise.

10

See my response here: