I set up a scheduled email so that it would look at each row and if the [Next Inspection Date] =TODAY()+30 it should send an email with the contractors name as a reminder. I now there is a few rows which it should flag but it is doing nothing. If i click on RUN it sends an email for every row. There seems to be know errors when i check the audit and test monitor and i am at a loss. If some one could help me it would be very much appreciated.
Also please ensure " Bypass security filter" setting is properly set, meaning please ensure , if there is a security filter in place, it is not filtering out the records intended to be used in the bot.
In that case, please set the " Bypass security filter" setting to âonâ
today() is a formula that changes every day. How about doing it like this?
[Inspection Reminder] = TODAY()
By adding 25 days to the [Next Date of Inspection], you can have [Inspection Reminder]. This way, it will serve as a friendly reminder just 5 days before the scheduled date. Its good with a virtual column.
Make sure there are rows expected to be generating the email. Your filter condition is checking that the [Next Date of Inspection] contains a date 30 days from TODAY(). In your example above, it appears it was run on Sept 17. 30 days from that date would be Oct 17, so your Bot will send emails ONLY for rows that would have had the [Next Date of Inspection] = â17/10/2025â. If no rows in the table have that date, then no emails are generated!
No, you donât need a slice. The filter condition in the Bot will do the same thing as a Slice. But do pay attention to @Suvrutt_Gurjar âs comment on Security Filters. If you havenât set up Security Filters on that table then you donât need to worry about it!
Yes strictly speaking, a slice is not required, as @WillowMobileSys guided.
Just sharing a thought behind suggesting slice.
Of late, there are many automation failures without automation monitor or audit log showing any error.
So thought was , let filtering of rows happen outside the automation infrastructure. In case table is large, the row by row filtering in the automation engine can be avoided.
Of course, we do no have quantitative data or probably means of insight into how much exact difference a filter in automation and one in slice will make.
On this, the Slice filtering will definitely need to occur on every data update to the device. In my opinion, it is an unnecessary hit to device-side performance.
A Scheduled Bot running once daily will only need to apply the filter once per day. The performance hit on the background Bot process is less critical.
There is still a concern should the table become VERY large - like tens of thousands of rows. The bot could hit a timeout due to long processing time. It is at that point I would look to other filtering means. Also by that time the app will have matured to the point that there are other table structures possibly requiring a completely different filtering method anyway.
Each table has about 150 rows by 20 columns very much doubt it will get any bigger as the data that changes is the reports linked to the contractor everything else stays the same.
thank you both for your help very much appreciated Jase
Would you believe it i set it to schedule for 4:05pm and it ran 1hr later and selected all the ones which are due at the end of Sept 10 days from now. Thank you for your help
You should be able to test a Scheduled Bot immediately by tapping the âRunâ button at the top of the Bot.
It should NOT take an hour for the Bot to trigger. It can take a few minutes if there are many other processes kicking off at that same time. Thatâs why it is best to set the run time at some odd time. You used 4:05 and that is good but even better is something like 4:17 or 4:23.
If you see consistently that Bots are taking an hour before they run, then that needs to be raised with AppSheet Support.
