Cannot commit 'activator' trigger into devops repository

[Andersenn]

Hello,

I'm encountering an issue when trying to commit a trigger item in Microsoft Fabric to a connected Azure DevOps Git repository. While all other items (such as notebooks, dataflows, and pipelines) are committed successfully, this specific trigger fails to commit.

An error message is displayed during the attempt, which I have attached to this ticket for reference.

Thank you for your support.

[Michele_Zanchi]

Hi, I'm struggling with the same error. I think that the problem in my case comes from one of these Activator ALM limitations:

The following components are currently not supported in Activator ALM:

• Eventstream  (rolling out)
• Real Time Hub Fabric Events (rolling out)
• Real-Time Hub Azure Storage events - not supported
• Data Pipelines (as target action)
• Power BI

Activator limitations - Microsoft Fabric | Microsoft Learn

I hope microsoft can offer a solution as soon as possible!

[v-sgandrathi]

Hi @Michele_Zanchi,

Thank you for sharing your experience and the helpful reference to the current Activator ALM limitations.

It’s Important to know that certain components like Eventstream, Real-Time Hub Fabric Events, and Data Pipelines as target actions are still rolling out or not yet supported within Activator ALM.

As you already gone through the Limitations document mentioned in your reply raising a support ticket as suggested may still be beneficial to track feature rollout progress and provide feedback directly to the Microsoft product team.

Thank you,

[v-sgandrathi]

Hi @Andersenn,

Thank you for reaching out.

Based on the error message, the TransformationMDTrigger is failing to commit to the connected Azure DevOps Git repository, while other items are committing successfully. This could be due to unsupported configurations in the trigger or temporary sync issues.

To begin, please try the following troubleshooting steps:

Refresh the workspace and try committing the trigger again.

Rename or slightly modify the trigger (e.g., edit the schedule or parameters), then attempt to commit.

Recreate the trigger manually and try committing the new version.

Ensure the trigger does not contain any special characters or unsupported expressions in its metadata.

If the issue still persists after trying these steps, Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

You can create a Microsoft support ticket with the help of the link below:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this helps, please accept it as a solution and drop a "Kudos" so other members can find it more easily.

Thank you.

[v-sgandrathi]

Hi @Andersenn,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[Andersenn]

Hi @v-sgandrathi,

Thank you for the follow-up.

The issue is not yet resolved. I’ve tried the suggested troubleshooting steps — refreshing the workspace, modifying the trigger, recreating it, and checking for any unsupported characters — but the commit still fails specifically for all the triggers I create.

Thanks again for your support.

[v-sgandrathi]

Hi @Andersenn,

Since you tried troubleshooting steps but still face the same issue, you can raise a support ticket for an effective solution as mentioned in the previous reply.

You can create a Microsoft support ticket with the help of the link below:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you,

Sahasra_CST Member

[v-sgandrathi]

Hi @Andersenn,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.