I am using {{zap_meta_human_now}} to update a date field in Airtable. I have my Profile Settings to America/New York for Eastern time.
When I test the action, the date and time “12/8/2022 2:30pm” is updated in Airtable.
When the Zap runs from an actual trigger, it instead puts “12/8/2022 9:30am,” a 5 hour difference.
Any ideas why it works in the test function, but not in the live Zap?
Best answer by CarlL
@CarlL
That is peculiar. Have you checked your Zapier Run History to see if that gives any insight and double checked the field settings in Airtable?
@Troy Tessalone The Zap specific settings are correct, so that wasn’t the problem.
@GetUWired Thanks, that showed me the problem. Zapier was giving the time in the correct time zone, but Airtable was reading it as being in UTC time. I don’t understand why that does not affect testing the action and I’ve not had the problem in other Zaps using Airtable. But for this one, I changed the use to {{zap_meta_utc_iso}} and now it is accurate in Airtable.
That is peculiar. Have you checked your Zapier Run History to see if that gives any insight and double checked the field settings in Airtable?
@Troy Tessalone The Zap specific settings are correct, so that wasn’t the problem.
@GetUWired Thanks, that showed me the problem. Zapier was giving the time in the correct time zone, but Airtable was reading it as being in UTC time. I don’t understand why that does not affect testing the action and I’ve not had the problem in other Zaps using Airtable. But for this one, I changed the use to {{zap_meta_utc_iso}} and now it is accurate in Airtable.
Thanks for swinging back around to share your solution with the community, @CarlL!
Appreciate you sharing the Airtable insight too, @Troy Tessalone! Super handy to know. 🤗
Early access
Next Gen Zaps
Build and deploy automations from AI tools you already use. With Agentic Management, if anything breaks, the agent diagnoses the issue and proposes a fix.