Hello Bubblers !
I have this strange behavior with date/time.
I have setup Meta appointmets to send appointments date/time to Make (ex integromat) and send it to an endpoint in Bubble.
I added a “log” entry to check what time is sent to bubble :
I’m scheduling an aPI WF to make some action on my user :
like this action :
But when I 'm checking DB entry, this is 2h +
same on display in front :
Maybe some of you wil have an idea on how to handle this ?
Thank you !!!
hi, do you think it may be related to this?
Hey there!
@samnichols is correct! More precisely, we take the timezone from whatever browser initiated the first request to hit our servers. When you have a data trigger or backend workflow that is triggered from a backend workflow, that data trigger or backend workflow “inherits” the timezone of whatever triggered it. You can find more details on this forum post as well as details for what we do when an API workflow is triggered externally (e.g. not from Bubble)
1 Like
jona
June 26, 2023, 5:41pm
3
Hi! Thanks for the fast reaction. I dont see the link between my case and this, can you explain it?
the time is off by 2 hours.
this appears very random or very systematic meaning how the bubble system handles timezones incoming from other apis could perhaps be relevant meaning perhaps timezone info has to be parsed over to bubble as well.
1 Like
Server Side actions are all executed in the UTC timezone (and rightly so, preferring any single timezone, or having that as an app setting would be a nightmare). So all date string parsing is relative to UTC for server-side actions. You will need to use one of the tools to parse in an explicit timezone, or store data as UNIX timestamps.
1 Like
probably, but after reading all the post and test something I cannot find any solution to this.
in make I send this :
In Bubble, in my WF endpoint I save the date like this :
then sending the date to another WF :
and go this (+02h ?) :
and when sending an email referencing the date it is 10 again :
this drives me crazy !!!
From the make Screenshots looks like you are not yet parsing the timezone over as suggested by both of us
I fixed this by using a dynamic timezone in the BWF as user/club/address TimezoneID
1 Like
system
Closed
September 4, 2023, 4:26pm
9
This topic was automatically closed after 70 days. New replies are no longer allowed.