I am trying to get recurrence to work on my workflow. I looked at the following:
And that fails to validate properly now (even using the EXACT text used in the example).
The only format I am able to get to work is UTC format with something like:
Of course once you specify UTC it will ignore any Time Zone automatically. This is behavior I understand and accept.
If I wanted to say have the workflow start for the first time (or preferrably every day) at 8AM CST (regardless of whether it's daylights savings), what would the format be if I selected CST for the time zone? I tried various things but using an offset -07:00 doesn't work via validation and isn't DST proof either.
As a secondary question, as many have stressed how limited the scheduling is for flows (yes I realize it's in preview), is there any documentations on how to kick a flow off from the Azure scheduler? This would likely allow much better scheduling and such and give more time to the flow team to complete such features while letting us flow people schedule with complexity.
Thanks in advance for the help!
The format under the Start Time field should always be in
If you have specified the time zone, then the Start time should be the time in the time zone you have specified, there is no need to add offset.
For your second question, I am not sure I understand it clearly.
If Recurrence is not suitable for your scenario, you may consider take use of the other triggers, such as Email arrives, or event creation, making the other trigger in a schedule should also be a proper way to schedule Flow running.
For Example, we have an email send to some special address automatically every time, then we could build flow based on this Email arrival, then trigger the following actions.
If you have any further questions, or if I have any misunderstandings, please post back.
First, thanks for your fast response to this post. Let's for the moment ignore the second question and other options outside of MS Flow and only approach the formatting issue in my initial question. I can always create a new thread in the correct place. Also be aware that I have developed in the MS stack for decades but I want to provide solutions to customers that they can configure themselves for better value to them.
Unfortunately your response for this question is not sufficient. If there are not any other formats allowed besides what you posted, then there is either a bug or the time zone field should be hidden or removed as it has no purpose. Let me explain by an example workflow I used for testing (it simply does nothing but send a fake test email currently):
The particular run information for this workflow is:
Recurrence Trigger Settings -
Interval: 1 [I'm expecting this to run this workflow every day starting from the start time unless its in the past]
TimeZone: Central Standard Time
Run information -
This flow was activated on April 30th at 4:00PM, therefore missing the first run date because it had passed.
The flow RAN on 04/30/2017 8:50PM Central Time (i may be off an hour on this).
The issue -
Based on the information and when it ran, it's clear the start time was taken only in UTC context and the Central Standard Time was ignored completely. If you look into official formatting of datetime fields, it becomes evident why. Whenever you append Z to the date time, it AUTOMATICALLY makes it Universal Coordinated Time (UTC). Now that behavior as I mentioned before is understandable (if you are specifying UTC directly within the formate it should ignore everything else), but without allowing any other format, the way the trigger is developed, there is no point to ever having a time zone field in it.
So the main question maybe is better asked:
Why have Time Zone as a field in Recurrence when only UTC date/times are allowed and the Time Zone is ignored.
Why aren't other formats allowed anymore (they were as mentioned in the link above) that are relative to the Time Zone field?
Thanks again and hopefully this clarifies things!
Apologize for the late response.
Yes, the format is in UTC format, and this is a known issue.
For the TimeZone, I will forward that and see if there are any changes could be made.
I will let you know once I have any response back on this.
Facing similar issue with utc - it in not allowed, which does not make sense to me.
Utcnow() is one of the key functions in expression.
Please can flow / O365 allow posting an event in utc and do the time zone conversion for us, similar to when I do this in the calendar itself?
There are some important facts missing from the Microsoft Flow official documentation.
There is better documentation for Recurrence available in the Azure docs
which provides much better documentation for the Recurrence than the Flow docs.
Watch the event on demand for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.
Continue your learning in our online communities.
Features releasing from October 2019 through March 2020.
Fill out a quick form to claim your user group badge now!
Learn how to build the business apps that you need.
Find out where you can attend!
Watch & learn from the Flow Community Video Gallery!