An issue this tip tries to address:
Occasionally the bot runs partially and times out on certain steps.
At times , we app creators or the app users experience that the AppSheet app in general is working but the bot has timed out on a step and partially run.
Assumption in this tip: This tip assumes that the bot running has not totally stopped but it partially runs and the main long running step has timed out. This means it starts but times out on an intermediate step.
Show More
Recently we experienced a situation wherein the bot ran partially when invoked from a grandparent table. It successfully added records to the child table but the step to add records to the grandchild table timed out. Of course it timed out when there were server slowness issues on 20th June 2025. Other times it was running successfully.
While the Enterprise subscription allows to access the audit logs and one can further process those, the following approach can help Core plan app users. It also suggests an ( app ) user friendly approach wherein one may get a sense of successful running of the critical bot steps.
The approach
Show More
The approach suggests adding one text column called say [Report_Log] in the table from which the bot triggers.
A) Basically the first step of the bot sets the text in the [Report_Log] with an action that the bot has started and the completion is awaited. The first step highlighted in yellow in the diagram below.
B) This step is followed by the normal step such as sending report or adding/ deleting rows , calling and api etc. This step is highlighted in light green in the diagram below. The user is basically interested in knowing if this step ran well or not.
C) The final step again sets the [Report_Log] column with an action to a value that the bot is completed. if the normal step mentioned in B) above does not run , this [report_Log} step C) also does not run. This lets the app user know that the bot’s normal step has not run. This step C) is also highlighted in yellow
Short Demo
Bot did not run message capture
Show More
The GIF below shows the testing of this concept. Whenever the column [Enable_Report] is set to “Disable” , the condition in the test bot does not allow the report step to run. The message in the first step A) captures that the bot has started. But since the steps B) and C) do not run, the bot incomplete message set in the first step A) is shown to the app user. Please see this for the record Ann Adams.
Bot successfully ran message
Show More
On the other hand when the column [Enable_Report] is set to 'Enable" , the report step runs, and the last step C) that sets the [Report_Log} to successful running also runs and lets the user know that the bot has run successfully. Please see this for the record Bob Barker.
This way the app users can know if certain bot’s main step ran successfully or otherwise on a particular run.