[image] As shown, I’ve set this automation to kick-off every Friday …except June 14th is a Saturday [image] The resulting actions are therefore late by a whole day and are wrong

UTC +10 I wouldn’t have thought it’d matter considering how the automation is worded

The way it works is it converts it to UTC and saves it in the Fibery backend as UTC. So I think something in the conversion isn’t working as it should… No idea. Some funky stuff is going on here. Also noticed that the time picker starts from 10:00 in your timezone… then anything after 00:00 is set …

That seems to be the bug. Rather than starting at 00:00 and going through to 23:30, the moment time wraps in the selector it begins treating everything after 00:00 as the following day.

Bump. This is still an issue for our team. Email notifications (reminders) are being sent a whole day out—kind of pointless for reminders, no?

I figured this as UTC is behind. I have to factor this in. Automations don’t work for date comparisons, even if the date is stored as a Date and not a Datetime (5 Nov =/= 4 Nov) I’ll do this by instead of relying on a schedule, relying on a reminder trigger on a per-user basis, by storing a timezon…

[image] AdVhPkgKad: Today() only calculates ONCE, and there is no way to use the current time in formulas. Correct. This is because the formula service would be overloaded if it had to recalculate every second (minute?) of the day . [image] AdVhPkgKad: Automations don’t work for date comp…

I noticed this last week but was able to work around it. I was creating a chron job that needs to run once a year on daylight savings “day”. I wanted the automation to run early on Sunday mornings but it was almost as if the Week day picker was treating Saturday and Sunday as the same option. So I …

[image] Chr1sG: In general, date comparisons should work fine (if comparing a date with a date) but comparing a date with a datetime requires typecasting If the automation filter is set to “where date is today”, it’s wrong. Every time. Period. Not once has any scheduled automation I’ve set u…

Which is why if I schedule something to run at 12PM it will work, no problems, but picking any time before 11AM (due to the 11 hour UTC offset) will cause this out-by-day error. This is just not acceptable for our business. Midday is half-way through the working day for the people who need these no…

[image] Chr1sG: Correct. This is because the formula service would be overloaded if it had to recalculate every second (minute?) of the day . And regarding this, everything at the UTC changeover grinds to a complete halt already (formulas pending, automations stalling, user experience down the…

Date out by a whole day

Bugs & Issues

Topic		Replies	Views
Scheduled Automation: "tomorrow" / "today" / "yesterday" filters appear to be off by one day Ideas & Features automations	5	49	July 18, 2026
Twitter post about potentially new Fibery settings	9	453	January 23, 2024
Formula field calculating on date is returning wrong result Get Help	7	95	February 19, 2026
Timezone offset calculation API & Programming	9	5267	April 3, 2024
Rules are not being run on the schedule Bugs & Issues	5	301	March 21, 2023

Date out by a whole day

Related topics