Forum Discussion
Advocate IIScheduling a Microsoft Fabric Pipeline with Specific Time Intervals
Hello JibinSebastian
I am assuming your Fabric capacity is paused outside business hours (7AM - 7PM) to save costs. If you set your pipeline to trigger every 10 mins, the trigger will run fine but your pipeline will fail because your capacity is found Paused.
Secondly, Power BI semantic model enforces a 30 min minimum interval window, so the service backend will block it, regardless we tried a 10 min interval. Maximum 8 scheduled refreshes per day per dataset is allowed.
Considering the above, I suggest you design it the following way:
Orchestrator pipeline
Notebook activity (checks against weekends)
Scheduled every 10 minutes, business hours onlyPipeline 1 – Data ingestion (trigger if parent Notebook passes as True)
Copy DataPipeline 2 – Semantic model refresh (runs after pipeline 1 success, engine may skip or throttle if run within 30 mins)
Semantic model refresh activitySchedule as discussed in previous post:
- Frequency: every 10 minutes
- Time window: 07:10–18:50
- Time zone: EST
Continued ContributorI think u just run the 10‑min window and let the first Notebook line quietly step out on weekends, ’cause Fabric’s trigger can’t keep weekday‑state at dispatch and this path stays the most stable in real runs.
JibinSebastianCould you please explain a bit on this.
I didn't quite understand that
- Kagiyama_yutaka
sure. I just meant Fabric’s trigger can only fire every 10 min and it can’t check weekdays or time windows by itself. so let the trigger run, and add one line in the Notebook to skip if it’s weekend or outside 7:10–18:50.