Time is wrong in NOW()

[lailah]

I have a formula field containing NOW() and nothing else. The field is showing the wrong time. Right now it's 3:02 a.m. in the desired time zone (Eastern Daylight Time), but the field shows 2:59 a.m. I've attached a screenshot showing the difference between the displayed time and my computer clock.

Weirdly, when I first set it up but hadn't yet changed the time zone from GMT, it was 2:59 a.m. but the field showed 6:03 a.m.

Is this a known bug? I need this field to calculate the difference between when an item is due and the current time (that is, how many days/hours until it's due), and the time does need to be accurate to the minute.

[TheTimeSavingCo]

NOW() doesn't update immediately I'm afraid, from the documentation:  

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.

--
I don't know of any workarounds to get accurate to the minute timings either I'm afraid, perhaps someone else will have an idea

[Steve_Haysom]

the only thing I can think of is to create another table with one record in it with a date modified field in it, and then use a script to update that record (or just update manually), and a lookup from each of the records in your first table to the date modified field in the second table. Then the date/time will be correct immediately after the script is run , assuming the script takes less than a minute to run!

[aundre_hamilton]

I know this has been a while now, but I figured out a way to make sure Airtable runs at the right time, ALL THE TIME. Unless they introduce something again to prevent or fix this. Check out my video. I am not sure if everyone here will get my response, but if the video is not there in the future, here's the solution:

1. Create these two fields: checkbox and last modified date, ensuring that the date and time are seen.
2. Go to automation and create an automation that matches a condition. This first condition will be, if the checkbox is without a tick (blank), then the action is to UPDATE that said field with a TICK.
3. Duplicate the automation and simply do the reverse. If the field has a TICK, the action should UPDATE it by removing the tick. Essentially make sure it's blank.
4. Turn on these automations and go back to your table.
5. Trigger it so that it starts.
6. The automation will indefinitely loop and the last modified date will update every 3 to 5 seconds. This will stop us from waiting for Airtable's 5 to 15 minute updates.
7. Now anything that you create that is time sensitive, use the last modified time.

[TheTimeSavingCo]

Hmm, wouldn't this burn through the monthly automation quota?

[aundre_hamilton]

Thanks for this!

Yes, it's possible. I just realized that there's a limit here. However, my aim was to find somewhat a solution for those who require time sensitive triggers. In the video I mentioned having the ability to turn it on and off so as to have absolute control. Implementing the on and off feature could help to minimize reaching the limit. Maybe using Airtable's current time, NOW() function, can be used as a trigger to start updating the last modified time, then stop it when needed.

In the end, users simply have to use this method wisely, especially with the limits now in view. I'll probably try to find an even better solution, maybe a webhook from another site to update Airtable's last modified time.

Thanks again! I appreciate it!