Current scheduling options for Data Pipelines in Microsoft Fabric are very limited, supporting only minute-based, hourly, daily, and weekly triggers, and lacking robust interval configurations or mu...
Just voted for this. I had expected that Fabric would have an enterprise scheduler that supported much more out-of-the-box flexibility in date/time based scheduling, specifying predecessors etc., but alas not. Although I do like the idea of Triggered events - on their own however they're not of much use to me unless I can combine multiple events within the one rule, and even then I'd want include a schedule within the rule so that all conditions are satisfied. E.g. If I want an ingestion Pipeline to run only after 1) completion of one or more dependant Pipelines and 2) input files have arrived in my WS folder and 3) daily after 6pm - then I think I'd need to build my own scheduling logic.
