Share
ReportI have a Power Automate flow that iterates over a rolling date range (using a Do-Until loop) and evaluates each date against a set of conditions. For each date in the loop:
- The flow determines whether I am scheduled to work that day.
- If the result is false (I do not work that day), the flow then checks my Outlook calendar to see whether an “Unavailable-Not Scheduled” all‑day event already exists on that specific date.
- If such an event already exists, the flow does nothing.
- If no matching event exists, the flow should create a new all‑day calendar event for that date.
The date being evaluated is stored in a variable (e.g., CurrentDate) that updates on each iteration of the loop.
The main issue I am encountering is with the Outlook “Create an event” action (V3/V4). Although the flow logic works correctly and the rolling date updates as expected, Outlook does not accept dynamic values, variables, or expressions as the Start Time and End Time when creating an all‑day event. The action appears to only accept literal date inputs, causing the flow to fail at runtime when attempting to create events programmatically for dynamic dates.
I have verified that:
- The rolling date variable is correctly formatted (
yyyy-MM-dd), as is every date in this entire flow. - Calendar events are successfully retrieved and filtered earlier in the flow
- The failure occurs specifically at the Create an event step when attempting to use a dynamic date value.
I am looking for guidance on:
- Whether there is a supported way to create all‑day Outlook events using dynamic dates in Power Automate
- Or whether this is a known limitation of the Outlook V3/V4 connector when used with all‑day events and variables
Any recommendations on supported patterns or connector limitations would be appreciated.
All responses (
Answers (
594
