Hello @Gokul ,
I was able to reproduce the issue from my end.
If you look at the below screenshot, my tumbling window trigger got failed and the next trigger is stuck at "waiting on dependency". It will wait for seven days before timing out.
The next trigger will start only after this trigger gets canceled or timed out after 7 days.
Even though I manually ran the previous runs, "waiting on dependency" trigger didn't get started. So I have to cancel it for the next scheduled triggers to run.
In the below screenshot, I manually canceled the trigger(waiting on dependency one) then the next scheduled triggers started successfully.
Tumbling window triggers are a type of trigger that fires at a periodic time interval from a specified start time (basically when you want to process a time based data), while retaining state. Tumbling windows are a series of fixed-sized, non-overlapping, and contiguous time intervals.
These triggers offer a suite of features for complex scenarios like :
Dependency on other tumbling window triggers
Rerunning a failed job and
Set user to retry for pipelines
Here are the Limitations of tumbling window triggers
A tumbling window trigger has a one-to-one relationship with a pipeline and can only reference a singular pipeline.
If one of the dependencies triggers fails, you must successfully rerun it in order for the dependent trigger to run.
A tumbling window trigger will wait on dependencies for seven days before timing out. After seven days, the trigger run will fail
I hope this helps.
- Please don't forget to click on and upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
- Want a reminder to come back and check responses? Here is how to subscribe to a notification
- If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators