Some scheduled processes didn’t run yesterday & today in my app. What is more, some run twice in a row. Did anyone else experience that?
2 Likes
Have you checked the Scheduled Bot criteria to see if maybe the conditions were NOT met for the Bot to run?
I have never experienced this kind of behavior unless it was testing of the Bot and the Run button was tapped manually. Could that have happened? Anyone else with app access the might have ran the Bot manually?
1 Like
Thing is, those bots run since last year, and since ~12 months situations like this one happened twice. I already contacted support, and they escalated that to the specialist team. In my opinion the problem is on appsheet end.
- I checked that and conditions are met
- We weren’t testing the bot, the app is deployed since last year and nothing changed since few months in those modules/workflows
Thanks for reply!
1 Like
I have a same problem in scheduled bot. But use the “Run“ button, it still work. In my case, I just set a schedule bot what I want to use the Apps script at the time. Didn`t run the processes on setting time from the day before yesterday, but!! that is runed on the time later then setting time over about 90 mins when I checked back. Anyone can help us to fix the problem? Thx.
Yeah, exactly the same on my end. In one of my apps it was triggered with the same delay ~90 minutes. I contacted support, they confirmed that something is going on and escalated the case to the “specialist team”.
4 Likes
Thank you for your reply. And thanks for your contacted to support team. Actually, my teammate was ask this case with Gemini. And get the answer, that were too many tables(one bot is counted for one table…orz…) in our App right now. So were trying to drop some Bots and waiting. Ifthat will be work. Ill come here and tell you. If you got some answer from support team, and if you dont mind to share. Could you plz share the answer with we in this chat? I`ll very very appreciate it.
Hello Mateo,
Can you give us more details about what your bot does (ex: an email is send or a column is updated) and how many lines need to be executed?
It sends requests using webhook task type in the bot. The bot is triggered every hour and usually processes around 10 records at once. It was all good, working fine till Wednesday.
1 Like
A webhook to what API? Have you checked the automation and audit logs for any indication of an error in either place?
Another couple other things to note:
- The Scheduled time is approximate. When the bot is triggered it will get placed on a queue of processes to be executed. Depending on how many were triggered at that time and how long the processes take before yours, it can be many minutes before your Bot is actually picked up and processed.
For this reason it is advised to select ODD schedule times. Avoid top of the hour when MOST are likely being triggered. Avoid common times like 15, 30 and 45 minutes.
Instead schedule times like at 27 or 56 minutes past the hour. These will occur at the end of potentially significant trigger window BUT just before another MAJOR trigger window.
- If you have any Delay steps in your Bot they can cause unexpected significant delay’s when their condition is not met. One common problem is waiting for a change made by another Bot or some user action. The condition will never be met. Bot’s operate on the state of data at the time the Bot was triggered. External updates will NOT impact a Bot that is already running.
I hope your issue is identified and resolved soon!!
2 Likes
I checked the destination API logs, there are no requests. The same on automation monitor and audit logs. Those workflows just don’t run for some reason. I cannot understand why it was working fine since May last year and suddenly stopped. When I test my conditions they are met. We don’t set it for specific time, those bots are the “hourly” ones. Even the one that is set for specific time should run at 6:07 am my time. I don’t get it. Something is off in my opinion. Thanks for all help and tips!
My scheduled bot also started to run 90 min later then planed. AppSheet Monitor shows it started from the 18th Feb 2026, I’ve also mailed support, they didn’t reply it was a known bug.
Can you show us what your conditions are?
Keep in mind the conditions need to be considered at the time the Bot was run. If some conditions are frequently changing, a test may not prove anything. I rarely rely on the “Test” feature.
The hourly Bots still have an ability to specify the “minutes past the hour”. See image below
3 Likes
Exemplary condition:
AND(
[startDate] = TODAY() + 1,
ABS(
TOTALSECONDS(
([startTime] - TIME(NOW()))
)
) <= 360,
OR(
ISNOTBLANK([customer]),
ISNOTBLANK([customerGroup])
),
[type] <> “Inne”,
[type] <> “Wydarzenie całodniowe”
)
Minute of the hour:
1 Like
These seem a little odd together. The first line looks for things starting tomorrow.
I believe Bots do not assign TODAY() and NOW() until they actually execute.
The ABS(…) <= 360 part is looking for items that are within 6 minutes of (6 minutes before or 6 minutes after) the run time of the Bot. So assuming the Bot runs at 1:55 PM, it will be looking for items with [startDate] of TOMORROW and a [startTime] between 1:49 PM and 2:01 PM. However, if the Bot is queued for 20 minutes and actually runs at 2:15 PM, then it will be looking for TOMORROW items with[startTime] between 2:09 and 2:21.
It gets more complicated if the run time was expected to be 11:55 PM and there is a delay and it doesn’t run until after Midnight. TOMORROW is then bumped to the next day.
Questions come to mind, why only a 12 minute window once an hour? What about all the items that have TOMORROW startTimes between each of the 12 minute windows? Are startTimes restricted to certain times?
In words, what are you actually trying to accomplish with this portion of the expression?
************
Additionally…
Be careful with Negative logic. This part of the expression will be true if AT LEAST ONE is not blank. If your intention was for it to be true ONLY IF BOTH are not blank then you would want to use AND instead.
4 Likes
Wow, thanks for your time! It seems you are really into this topic to help me. Really appreciate that.
- I have events table where I store records that can start at 00, 15, 30 or 45 minute of the hour
- Every ~24h before the event, app sends reminder to the clients via webhook to our text messaging service API
- Bots are set for 10, 25, 40 and 55 minute of the hour
- The reason for this ABS() function is that I know it will never run at the exact specified time so we decided to leave this 6 minutes space for the bot
- It was working fine every day since May and suddenly stopped
- Yesterday I was able to see in the logs that few executions worked but for example if there were 4 events at the same time, bot sent only reminder to one of the client instead of four of them despite that conditions were met for all four of them
- As for ISNOTBLANK, it is okay. Always either customer or customerGroup is filled in, no matter what - we validate that
3 Likes
Hello Mateo,
Regarding the execution of your bot, it depends entirely on the execution time of your task, which means that even if there are only 4 lines to execute, for bots with scheduled events If the total execution time exceeds five minutes, the AppSheet service aborts its execution.
I understand that you said it worked before, but sometimes apphseet may just be slower than usual, or simply having more data may affect the process (in this case, make sure that the “Bypass Security Filters” option is not selected or limit the use of the function like select or filter). You must therefore ensure that your task does not take too long and that there are not too many lines called at the same time.
Regarding the use of ABS function, I would recommend using Boolean columns instead (e.g., schedule_00, schedule_15) to ensure that the record is called at the right time.
3 Likes
Thank you, but during one period (00, 15, 30, 45), there is not more than 20 records as of now never. We filter the input at start. If it would be the case then I would see those errors in monitor but there is nothing. It just doesn’t run. Support didn’t reply “it is on your end, go fix your logic”. They open my app few times a day, every day. I will let everyone know once it is fixed and I find out what is going on.
2 Likes
Same issue here. Bots that have ran the same for over a year now are currently not running or firing twice.
3 Likes
Support ticket has been opened and escalated to specialist team.
5 Likes
Since a second person has also noticed the same issue, it would seem it is indeed that it must be an AppSheet issue recently introduced.
For what it’s worth, on your notification logic, it seems it has the potential of missing notifications on events. A recommendation I can make here is to add a column to your Events table for “Reminder Sent”. Then change your Bot to send reminders for any Event where Start Date and Start time are <= 24 hours from NOW() and ISBLANK([Reminder Sent]), send the reminder and record NOW() in the “Reminder Sent column.
This will ensure that any Events that might have just missed the last hourly cutoff are picked up on the next run. The added benefit is that you can clearly see WHEN that reminder was sent for that Event, should there ever be any issue.
That expression would be something like this:
AND(
ISBLANK([Reminder Sent]),
TOTALHOURS(DateTime([startDate] & “ “ & [startTime]) - TODAY()) <= 24.0,
<... your other logic...>
3 Likes