Pipeline triggers not syncing with DevOps repository

[sawilliams]

Hello, I have the following problem:

I created a workspace with three notebooks, three lakehouses, and one pipeline, and then synced this workspace with a DevOps repository. So far, everything works fine—I can see any changes I make in the UI and properly commit them to the repository.

However, my issue is that I created a trigger for the pipeline to run every week, but I don’t see this change reflected in Git control. This makes me think that the trigger configuration is not being updated in the repository.

Am I correct in assuming this?
How can I save this trigger in the repository?

[v-prasare · Accepted solution]

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

[v-prasare]

@sawilliams As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

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

[v-prasare]

@sawilliams, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

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

[v-prasare]

@sawilliams, 

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

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

[v-prasare · Accepted solution]

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]

Thank you for your response. Do you recommend a best practice for creating these triggers in the pipelines we are setting up in the production environment, while avoiding manual interaction? Fabric rest api?

[v-prasare · Accepted solution]

@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