Tighter control on timing of hourly scheduled pipeline triggers
D
Denis Lemire
Currently when creating a scheduled pipeline trigger, intended to run once per hour, there is no control as to when the trigger will execute within the hour specified. In extreme cases it can run close enough to the end of the hourly window to cause confusion or delays relative to expectations.
Per docs: "Why did my scheduled pipeline run later than expected?"
Although subsequent runs occur at a consistent time, greater control in specifying that recurring time is desired.
Eg) a narrower 30 minute or even 15 minute time range would be desireable
A
Alicent Hightower
Denis, have you or the team considered offering more granular scheduling options like specifying exact minutes past the [url=https://block-blast.io]Block Blast[/url] hour or aligning triggers with specific time zones to better accommodate workflows with tighter timing constraints?