Pipeline triggers not syncing with DevOps repository

Hi sawilliams,

Thanks for reaching Ms Fabric community support

Triggers are considered environment-specific configurations and are stored only in the Fabric service, not in Git. This behavior is similar to how Azure Data Factory manages triggers.

pipeline triggers are not included in the repository when using Git integration in Microsoft Fabric. Only pipeline definitions (activities, parameters, and linked services) are tracked in source control, but triggers are not version-controlled within the DevOps repository

Thanks,

Prashanth Are

sawilliams, You can automate trigger management in Microsoft Fabric using the REST API to create, update, and monitor triggers, ensuring consistency without manual intervention, even if they are not reflected in Git control. If weekly trigger settings are missing from Git, use API-based deployment scripts, check for pipeline parameterization limitations, or manually export and reimport trigger configurations using JSON.

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query