Today my Automation was interrupted in the middle of processing.
(Don’t worry, it’s not a problem that will affect production, as it’s still being tested.)
In addition, after copying the app to my Enterprise account, I ran the same process with the owner changed, but I got the same error (the process stopped after 121 seconds).
I would appreciate if you could advise me how to make this Automation work correctly.
I believe there is also protection against infinite looping that can stop the process before 5 (or even 2) minute limits. Is there any possibility that your process has created an infinite loop?
The Execution Time is the bot execution time. It does not include time for actions that might take place before the Bot execution like writing the data to the backing store. You can check the performance analyzer to see the full distribution of time for this execution.
I m still bit puzzled to see how this 5 min would be calculated. can you eaborate bit deeper using some use cases?
At the same time, on other post, you mentioned there is 2 min limitation over the bot, so this make me puzzled what those 2 mins | 5 mins restrictions are working together behind our scnene.
I believe there is also protection against infinite looping that can stop the process before 5 (or even 2) minute limits. Is there any possibility that your process has created an infinite loop?
Thanks,
Since the process is a simple Automation that only copies VC values to physical columns, I think the problem is probably related to the amount of data.
With the same data schema and the same Automation, I have the following results.
10 rows: OK
100 rows: OK
1000 rows: NG
40000 rows: NG
As a conclusion, I have solved the problem by exporting the CSV containing the VC values from AppSheet and editing it directly on the spreadsheet.
There are times when our want to convert VC into a physical column, right?
I would like to know how many rows of the data set can be processed by AppSheet.
Since this Automation is a Step that only copies the VC values, I believe that almost no other processing occurs.
I measured it at the actual time, and Sync finishes in about 2 minutes, but Automation has an error.
This leads me to believe that in addition to the 5-minute execution time limit for the Bot as a whole, there is a 2-minute execution time limit for each Step.
Thanks @Takuya_Miyai for sharing your testing and result.
Dan_Bahir:
It does not include time for actions that might take place before the Bot execution like writing the data to the backing store.
I tends to believe that BOT limit is imposing restrictions, even for the time required to fire the action to change data, even though @Dan_Bahir is advising they are excluded, otherwise we are not able to explain your test result logically.
Your bot config is just super simple, nothing is complex. Just to fire action against number of the row should only be taking time to execute. If data change takes time (2 min?) on the server and backend, and once it reaches to 2 min bar, BOT stop all the pending jobs, and just throw error.
This tells me we are not able to employ BOT for any use cases to update the row data against even hundreds rows.
There is a 5 minute deadline for completion of all requests to the AppSheet server. That includes ones that trigger bots.
During the execution it periodically checks whether it has exceeded the 5 minute deadline, if so it will stop calculation and return an error.
Thank you very much for added the video it is very odd. Please create a ticket so that we could investigate why it is timing out after 2 minutes.
