Using the NOW() function in a formula no longer updates the time reliably, even after refreshing the base. It only returns the original time that the formula was created, but then it doesn’t update reliably beyond that.
I’m specifically referring to a formula that just has this as its formula:
I’ve noticed that within the last few days, this brand new disclaimer was added to the formula reference page for both the NOW() function and the TODAY() function:
***The results of this functions changes only when the formula is recalculated or a base is loaded. They are not updated continuously.
Forget that this sentence has several grammatical errors in it. The real problem is that the described behavior is incorrect. (And the behavior has changed on us.)
I created this formula:
NOW(), and it starts off with the current time. But then, I refreshed my web browser over a period of 5 minutes, and the
NOW() formula didn’t refresh at all.
Then I re-read the new disclaimer that the formula is only recalculated when a base is LOADED — so I went to the home screen and reopened the base, and no change.
Then, I completely logged out of Airtable and logged back in again, and Airtable still didn’t update the
NOW() formula at all.
After about 9-10 minutes, I hit the refresh button on my web browser, and the function finally updated with the proper time.
Also, @Justin_Barrett: didn’t you figure out recently that
NOW() would refresh on their own in the background, even if nobody launched Airtable or even if nobody was using Airtable? Looks like they’ve possibly changed that behavior, so that behavior might now potentially be gone?
If the NOW() function and the TODAY() function really don’t update on their own in the background anymore, then this new behavior could negatively affect any sort of external automation that depends on time triggers.