deployment pipeline copied over refresh schedule

Hello Jeanxyz,

According to Microsoft Fabric documentation, deployment pipelines do not transfer or activate refresh schedules when moving artifacts (like notebooks) between workspaces. This is by design: the deployment process focuses on metadata and content, not operational triggers like scheduled refreshes.

However, what you’re seeing—where the refresh schedule appears in the production workspace but is not enabled—is consistent with expected behavior. The schedule metadata (e.g., timing, recurrence) is copied over, but the execution trigger remains disabled until manually activated.

What to do:

1. Open the notebook → Schedules panel in PROD and confirm all schedulers are Disabled.
2. If you don’t want scheduler configs cloned, remove the scheduler before deploy or delete it post-deploy in PROD.
3. If you do want it active, explicitly Enable the schedule in PROD after verifying connections/permissions.

This aligns the behavior you observed (schedule present but disabled, with a few failed entries) with the new scheduler CI/CD feature design.

Hope it can help you 

Best Regards,

Antoine