This function updates when the formula is recalculated, when a base is loaded, or otherwise roughly every 15 minutes when a base is open. If the base is closed, it will update approximately every hour only when the base has time-dependent automation triggers or actions, or sync dependencies.
Airtable has now added scheduling into Automations, and I would highly recommend completely rebuilding your Automation from scratch using this new scheduling feature.
Their new scheduling feature is “mostly” reliable & consistent (97% reliable), but unfortunately, their NOW() function is very unreliable & inconsistent.
Even though their support article mentions this NOW() inconsistency, my real-world experiences have been significantly worse than what they outline:
When I use the NOW() function, it often doesn’t refresh for 75 minutes or longer when the base is closed, and it often completely skips over days altogether, meaning that it often doesn’t refresh for 48 hours.
So for the most reliability that you can get out of Airtable natively, I would rebuild with the scheduling trigger.
However, for 100% reliability, I would suggest moving to a professional automation platform like Integromat. (Note that I am a professional Airtable consultant and a Registered Integromat Partner, and the Integromat link contains my personal referral code.)
Thank you for the explanation.
My problem is that I want to post to a FB page on times I enter in the record itself. Therefore, the scheduling option seems not to work for me because the “One Time” option in scheduling allows me only to enter a specific time. But I want this time to be read from the record itself.
I tried the Now() function in different scenarios, but it failed me.
Is there a way to accomplish my goal?
Assuming you already figured out the system for calculating those times inside your base? Should be easy, just do a when-record-matches-condition automation instead. You might just want to run it a few times per day to check for new times to parse, depending on what exactly you’re trying to do and your base design.
Thank you for your reply.
My problem seems to be in the now() function and its irregular update pattern.
Therefore, I am not able to use it to compare the date and time field I have with the now() function to trigger the condition.
There really isn’t a way to get NOW() to update more predictably.
This might be because an automation is not triggered if the record meets the condition before the automation is turned on. The record has to switch from not meeting the condition to meeting to condition while the automation is active.