How to schedule trigger when pipeline execution time greater than trigger time?

Question

Trigger created to run every 15 min on daily basis. In case first trigger takes more than 15 minutes to complete and second trigger starts without completing first trigger.

How to handle this scenario?

Which trigger (Schedule / Tumbling window) needs to consider for this scenario?

Answer 1

Hi @Anuganti Suresh
Welcome to Microsoft Q&A platform and thanks for posting your question here.

Scheduled Trigger
A Scheduled Trigger is a type of trigger that runs a pipeline on a schedule. It is a lightweight trigger that is used to run pipelines at a specific time or interval. Scheduled triggers are marked successful as long as a pipeline run started, regardless of whether the pipeline run completed successfully or not.

Use Case
Scheduled triggers are useful when you want to run a pipeline at a specific time or interval, such as every hour, every day, or every week. They are ideal for simple scenarios where you don't need to retain the state of the previous pipeline run.

Scenario In the scenario mentioned, a trigger is set to run every 15 minutes on a daily basis. If the first trigger takes more than 15 minutes to complete, the second trigger starts without completing the first trigger. This scenario is not suitable for a Scheduled Trigger as it does not retain the state of the previous pipeline run.

Tumbling Window Trigger

A Tumbling Window Trigger is a type of trigger that fires at a periodic time interval from a specified start time, while retaining state. Tumbling windows are a series of fixed-sized, non-overlapping, and contiguous time intervals. A tumbling window trigger has a one-to-one relationship with a pipeline and can only reference a singular pipeline.

Use Case

Tumbling Window Triggers are useful when you want to run a pipeline at a specific time interval and retain the state of the previous pipeline run. They are ideal for complex scenarios where you need to ensure that the previous pipeline run has completed before starting the next one.

 Scenario
To handle this scenario, creating a Tumbling Window Trigger with a start time and an interval of 15 minutes is recommended. This trigger type will ensure that the previous pipeline run is completed before starting the next one, thus avoiding the issue of overlapping pipeline runs. Additionally, the Tumbling Window Trigger will retain the state of the previous pipeline run, making it suitable for complex scenarios where you need to ensure that the previous pipeline run has completed before starting the next one.

Conclusion

 Scheduled Triggers are lightweight triggers that are used to run pipelines at a specific time or interval, while Tumbling Window Triggers are more heavyweight triggers that are used to run pipelines at a specific time interval and retain the state of the previous pipeline run. In the scenario mentioned, a Tumbling Window Trigger is recommended as it ensures that the previous pipeline.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.