Options for more complicated pipeline scheduling

Within your pipeline, you can add activities to check the current date/time and conditionally execute tasks based on more complex criteria.

One method would be to have a (say) daily schedule where the first activity runs something that determines whether the rest of the pipeline should get run.
Similar to the solution proposed here;

https://community.fabric.microsoft.com/t5/Data-Pipeline/How-to-Schedule-Monthly-Pipeline-Need-Last-Friday-of-every-month/td-p/4334757

If this helps, please consider accepting as a solution to allow others to find it more easily.

Hi christianunr,

We appreciate your query posted on the Microsoft Fabric Community Forum.

The direct scheduling options in Fabric Pipelines offer basic recurring schedules, such as daily and weekly, but with certain limitations on granularity. Unfortunately, direct cron-like scheduling functionality is not natively supported within the pipeline user interface.

To address more complex scheduling requirements, a viable solution is to use multiple pipelines. If the scheduling demands exceed the existing limits, you can consider dividing the tasks across multiple pipelines. Each pipeline can then be scheduled independently, enabling efficient distribution of tasks across different schedules.

If you find this response useful, we kindly request you to mark it as the accepted solution and provide kudos. This will also assist other community members who may face similar challenges.

Thank you.