My experience is that every time we need time based filters in automations it important to set time zone in the upper left corner under the name of automation.
Maybe another approach would be to use filter views and go from there.
“Tape workflows run in UTC to be universally applicable and non-opinionated.”
Depending on how you store times in the record (via Calculation / Workflow) it might get some differences. However - wondering why you need to change filters for more than one day. If its a timezone issue, I guess it should be solved within one day tolerance…
Also wondering, how frontend behaves when filtering records. Of course than a +/- 1 day deviation could probably happen.
Photos above are from the actual workspace where regular filters works by date just fine.
Creating collected fields in automation have filter to chose by two fields in 2nd workspace where you actually chose start and end date.
Not really sure if there is setting for workspace fields individual fields. Maybe by pulling and using 2 different dates field come all this difference in more than 1 day.
Also @Leo - is there a plan to add automation filter by date to be the same as workspace filters… Where you can choose “on and after” & “on and before” certain dates?
Ideally will be nice to have central timezone setting (like it has in profile) to work with every workspace or automation across the board.