Skip to content

Commit bb5154f

Browse files
committed
Add a recurrence trigger corner case
1 parent f15ea2f commit bb5154f

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/connectors/connectors-native-recurrence.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,11 +104,14 @@ The Recurrence trigger is part of the built-in Schedule connector and runs nativ
104104
> the first recurrence runs immediately when you save or deploy the logic app, despite your trigger's recurrence setup. To avoid this behavior,
105105
> provide a start date and time for when you want the first recurrence to run.
106106
>
107+
> When a workflow is deployed via ARM template with a Recurrence trigger and in 'Disabled' state, it will trigger instantly
108+
> upon 'Enable' unless the 'Start time' parameter is configured before deployment.
109+
>
107110
> If a recurrence doesn't specify any other advanced scheduling options such as specific times to run future recurrences,
108111
> those recurrences are based on the last run time. As a result, the start times for those recurrences might drift due to
109112
> factors such as latency during storage calls. To make sure that your logic app doesn't miss a recurrence, especially when
110113
> the frequency is in days or longer, try the following options:
111-
>
114+
>
112115
> * Provide a start date and time for the recurrence and the specific times to run subsequent recurrences. You can use the
113116
> properties named **At these hours** and **At these minutes**, which are available only for the **Day** and **Week** frequencies.
114117
>

0 commit comments

Comments
 (0)