Hello Experts,
We are trying to implement logic in Flow Designer for Visitor Management.
Requirement:
If the visitor's Expected Departure time has passed the current time, then we need to update an Overdue flag in the Visitor Registration record.
Current implementation:
We created a Flow Designer condition that checks whether Expected Departure is at or after the current minute.
Issue:
We noticed that the Flow seems to evaluate the time in UTC, while the Expected Departure value is being interpreted based on the user/session time zone. Because of this, the condition evaluates incorrectly and the Overdue flag is set to true earlier than expected.
Questions:
- Is this expected behavior for Flow Designer time comparisons?
- What is the recommended way to compare Date/Time fields with the current time in Flow Designer when time zones are involved?
- Is there a configuration or best practice to handle this within Flow Designer conditions?
Any guidance or recommended implementation pattern would be appreciated.
@Ankur Bawiskar @Arvid @_raj_esh
