cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jakubz
Helper II
Helper II

Trigger date every year

Hello,

 

Can somebody please help me with a date trigger which would send an email every year at specific date an time? 

jakubz_0-1629206815248.png

Can I set it like that ? 

 

Thank you for your answer.

1 ACCEPTED SOLUTION

Accepted Solutions

@jakubz 

 

According to the Recurrence Trigger documentation

the 

Property JSON name Required Type Description
         
Frequency frequency Yes String The unit of time for the recurrence: Second, Minute, Hour, Day, Week, or Month

 

I believe "Year" might not be supported

 

Instead of using Year, you may be able to use 12 and Month instead to make it run "once every 12 months"

 

820201-time-01.png

 

 

Same docs also state that :

 

Start time startTime No String Provide a start date and time, which has a maximum of 49 years in the future and must follow the ISO 8601 date time specification in UTC date time format, but without a UTC offset:

 

YYYY-MM-DDThh:mm:ss if you select a time zone

-or-

YYYY-MM-DDThh:mm:ssZ if you don't select a time zone

So for example, if you want September 18, 2020 at 2:00 PM, then specify "2020-09-18T14:00:00" and select a time zone such as Pacific Standard Time. Or, specify "2020-09-18T14:00:00Z" without a time zone.

 

Important: If you don't select a time zone, you must add the letter "Z" at the end without any spaces. This "Z" refers to the equivalent nautical time. If you select a time zone value, you don't need to add a "Z" to the end of your Start time value. If you do, Logic Apps ignores the time zone value because the "Z" signifies a UTC time format.

 

For simple schedules, the start time is the first occurrence, while for complex schedules, the trigger doesn't fire any sooner than the start time. What are the ways that I can use the start date and time?

 

And furthermore, according to the Patterns for start date and time

Start time Recurrence without schedule Recurrence with schedule (Recurrence trigger only)
     
     
Start time now or in the future Runs the first workload at the specified start time.

 

Recurrence trigger: Runs future workloads based on the last run time.

 

Sliding Window trigger: Runs future workloads based on the specified start time.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

 

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

 

You can set a start date and time in the near future - then it will run the first time on that date - next time it will run each "12 Months" from that start date and time. It should run at exactly that same time 12 months later from the first time it ran.

 

Check if it helps.

 

 

 

You may also find this post helpful:

schedule a flow to run quarterly, annually, and Biennially 

 

For example, setting a value of 16 Months works, but not 17 months according to above post, I can reproduce it even now (with possibly a difference in the wording of the error message):

 

820201-time-02.png

 

Since 12 Months is less than 17 Months, you should be fine for your use case @jakubz .

View solution in original post

3 REPLIES 3

@jakubz 

 

According to the Recurrence Trigger documentation

the 

Property JSON name Required Type Description
         
Frequency frequency Yes String The unit of time for the recurrence: Second, Minute, Hour, Day, Week, or Month

 

I believe "Year" might not be supported

 

Instead of using Year, you may be able to use 12 and Month instead to make it run "once every 12 months"

 

820201-time-01.png

 

 

Same docs also state that :

 

Start time startTime No String Provide a start date and time, which has a maximum of 49 years in the future and must follow the ISO 8601 date time specification in UTC date time format, but without a UTC offset:

 

YYYY-MM-DDThh:mm:ss if you select a time zone

-or-

YYYY-MM-DDThh:mm:ssZ if you don't select a time zone

So for example, if you want September 18, 2020 at 2:00 PM, then specify "2020-09-18T14:00:00" and select a time zone such as Pacific Standard Time. Or, specify "2020-09-18T14:00:00Z" without a time zone.

 

Important: If you don't select a time zone, you must add the letter "Z" at the end without any spaces. This "Z" refers to the equivalent nautical time. If you select a time zone value, you don't need to add a "Z" to the end of your Start time value. If you do, Logic Apps ignores the time zone value because the "Z" signifies a UTC time format.

 

For simple schedules, the start time is the first occurrence, while for complex schedules, the trigger doesn't fire any sooner than the start time. What are the ways that I can use the start date and time?

 

And furthermore, according to the Patterns for start date and time

Start time Recurrence without schedule Recurrence with schedule (Recurrence trigger only)
     
     
Start time now or in the future Runs the first workload at the specified start time.

 

Recurrence trigger: Runs future workloads based on the last run time.

 

Sliding Window trigger: Runs future workloads based on the specified start time.

Runs the first workload no sooner than the start time, based on the schedule calculated from the start time.

 

Runs future workloads based on the specified schedule.

Note: If you specify a recurrence with a schedule, but don't specify hours or minutes for the schedule, Logic Apps calculates future run times by using the hours or minutes, respectively, from the first run time.

 

You can set a start date and time in the near future - then it will run the first time on that date - next time it will run each "12 Months" from that start date and time. It should run at exactly that same time 12 months later from the first time it ran.

 

Check if it helps.

 

 

 

You may also find this post helpful:

schedule a flow to run quarterly, annually, and Biennially 

 

For example, setting a value of 16 Months works, but not 17 months according to above post, I can reproduce it even now (with possibly a difference in the wording of the error message):

 

820201-time-02.png

 

Since 12 Months is less than 17 Months, you should be fine for your use case @jakubz .

Thank you!

@jakubz 

 

Beware of one more thing, it might not work at all unless the Start Date is set to at least a few minutes in the future. 

You can see others who had this problem here:

Can't get recurrence trigger to work 

Make sure to note of this as well when making this kind of Flow.

If your Flow does not work after you save it and does not fire on the Start Date - make sure the Start date is not set to the past first, and then save it again.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

MPA Licensing.jpg

Ask your licensing questions at the Power Automate AMA!

Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.

Users online (2,995)