Has anyone faced this when scheduling multiple API workflows in one go?
I have an a front-end workflow that schedules 3 backend API workflows in one go as per screenshot below
Screenshot of each block below
Now this all looks relatively straightforward, basically depending on which time is set furthest away, that time would be picked right?
Well here’s the logs of what happened when this workflow was actually run. Note that the workflow date selected was 22nd September 2021 8:00AM
(Note: I’ve hidden the sensitive data, as only the scheduled dates are relevant to my question here)
From what I can see, the first max condition uses the workflow’s date, but then the subequent conditions start to treat Current Date/Time as 22nd September 2021 5:00am and then the other two workflows are working off this time?
Why is that? I would have thought current date/time would represent the time at which this workflow was being triggered?
Is this a bug or how Bubble is actually meant to work? Curious to hear what your thoughts are!