[DataFactory] - Start/Stop Tumbling Triggers does not repect recurrence

Gustavo Balbino 0 Reputation points
2023-02-01T16:43:27.6466667+00:00

Hello,

I'm trying to make the following senario work without errors

  1. Have 1 pipeline that copies incremental data if table existes and if not it creates me that table.
  2. Have 2 tumbling trigger, 1 for running throughout the day and 1 to running at night for saving costs.
  3. Have 1 Automation Account to start and stop triggers, with 2 schedules (07:50AM and 07:00PM).
    the script was copied from here, https://microsoft-bitools.blogspot.com/2021/11/adf-release-use-script-to-enable.html

Trigger Configuration same for "NightTriggers" the difference is the recurrence:

trigger1

trigger2

This should be straight forward, "DayTriggers" should run in recurrence of 5m, the lowest allowed, and the "NightTriggers" should run every 1h, but this is not happening.
Some evidence in the images:NightTriggers

"NightTriggers"

DayTriggers

"DayTriggers"

After let him run.
DayTriggers2

At 10:13 AM it started to run as expected (5m of recurrence).

Is this behavior ok? Anyone have this issue?
Help! :D

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,539 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ShaikMaheer-MSFT 37,896 Reputation points Microsoft Employee
    2023-02-03T15:10:33.79+00:00

    Hi Gustavo Balbino,

    Thank you for posting query in Microsoft Q&A Platform.

    Tumbling windows triggers creates windows of all intervals and try to run them irrespective of when you publish them. So, by the time of publish if you see some tumbling windows cross already then, that windows will start executing immediately.

    For example, let's say I created a trigger start date time as 9AM and reoccurrence set as 1hour, and I published that trigger at 11AM. Then in this case, 9AM to 10AM window and 10AM to 11AM windows will start running immediately after you publish trigger. You will not see much difference in execution start time of this triggers because these two windows already crossed by the time of publish of tumbling window trigger.

    Also, please note if pipeline concurrency is set to only 1, in that case for that pipeline only one execution will be available at any given point of time. So if two tumbling widows tries to run it, then still first one window will run and then only another will start.

    Please check below video to understand, tumbling window trigger better.

    Tumbling Window Trigger in Azure Data Factory

    Hope this helps. If above is not your case, then kindly share details of pipeline settings and also Night trigger configurations too to understand issue better.


    Please consider hitting Accept Answer button. Accepted answers help community as well.

    1 person found this answer helpful.