Good morning! I'm trying to build a flow that will change rooms from "Available" to "Reserved" and back to "Available", based on the reservation time against the room.
I convert the timezone from the SharePoint list to my local timezone, and am using that output as the trigger for the Delay Until action, but the flow runs right through the delay like it isn't even there.
Any thoughts on why this is happening and how to resolve it so the flow will actually delay until the timestamp? Thanks!
Delay Until is not delaying, flow is blowing right past it...
@Nived_Nambiar Understood on the UTC aspect; I've made some changes since then just to see what exactly the timestamps are and this is a screenshot of the flow after running:
My current time is 11:22, so it shouldn't even update the first one, but even with the correct timestamps it's not delaying. Thoughts?
Delay until will delay the flow until a specific time.
So the expression you have used formatDateTime(utcNow(), outputs('Print_Start_Time')) will make the flow to delay by current time and that is why it passed the action without waiting.
So just want to check - which time from sharepoint list you have to use here - start time or end time from sharepoint list ?
Was this answer helpful?
If yes, please mark it as the solution by selecting the checkbox in the discussion thread.
Your feedback motivates me to keep contributing. Thank you!
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
4
Share
Report
All responses (
Answers (
