How do Activator Alerts behave after deploying to different workspace

Hi  flickeringflash ,

You’re right that real-time dashboards don’t support deployment rules, and that does limit how much of this process can be automated. In the current platform, those dashboards treat their data source connections as fixed endpoints, which means they don’t remap themselves when you promote content through a pipeline. The only dependable way to make sure they use the correct environment is to update the connection in the destination workspace after deployment. Some teams handle that manually while others script it using the REST APIs, but either way it has to happen outside the pipeline because the feature isn’t supported for this dashboard type.

The same limitation affects alerts. An alert attaches itself to the tile and the exact query that existed when it was created, so if the tile changes or you promote it into another workspace, the alert doesn’t update along with it. I know it creates extra work, but at the moment the only reliable method is to recreate the alerts in the target workspace as part of your deployment process. Automation can help streamline this if you prefer not to recreate them by hand.

Thank you for your continued efforts in testing the approaches we’ve provided. Since some time has passed and several options haven’t produced the results you need, it would be a good idea to raise a support ticket with the Microsoft product team so they can take a deeper look at what’s happening in your environment. You can submit a request through the Submit a product support request page:
Microsoft Fabric Support and Status | Microsoft Fabric

If you do end up finding a resolution through support, it would be incredibly helpful if you could share it back here with the community, as others facing similar challenges may benefit from it. We appreciate your patience and encourage you to keep engaging with the Fabric Community whenever you need further support.

Best Regards,
Tejaswi.
Community Support