Forum Discussion
Helper IFabric Activator not generating Alerts
Hello,
I have set up several Fabric Activator alerts on reports which seemed to be working but stopped all of a sudden.
One of the alerts was to send an email when a measure in a table exceeds 80% for a row of data.
This alert seemed to work fine for about a month, I would receive an email when a particular row of data met the trigger. All of sudden, I stopped receiving any emails for all the alerts.
In activator, the alert shows as "Running" and there are no error messages but there are no activations happening either.
I tried to re-create the alert, which worked for the first day and sent me a heap of emails, but nothing since.
We currently have a Fabric Trial license for the Workspace where I have set the alerts, although the reports are in different workspaces.
The condition on the alert is:
Condition: Increases to or above
Value: 0.8
Occurance: Every time the condition is met
- Hi _Amy_,Based on what you’ve shared, this behavior usually occurs when the Activator service gets paused, something that happens quite often with Fabric Trial capacities. Since you recreated the alert and it worked briefly before stopping again, that strongly suggests the trial capacity may be going into sleep mode rather than there being an issue with your alert logic or the dataset refresh itself.Ask your admin/IT team to check the Trial capacity status and confirm that it’s activeThanks,Prashanth Are
7 Replies
Anusha66Advocate IV
Hi Amy,
I'd suggest you to first check to make sure the measure actually goes above 0.8. If the number stays above 0.8 the whole time, the “increases to or above” rule won’t trigger again.
The 2nd step could be going to the alert in Activator and looking at the Preview (using past data) and the History tab. This helps you see whether the condition should have triggered recently and whether the actions actually ran. You can also try “Send me a test alert” button may be. One thing I observed was that if the report or data model got updated, the alerts dint work. So I had to re-select the measure.
_Amy_Thanks for your reply.
In terms of (1) - the report has many rows of data in it, I only want an alert where a row increases above 0.8 once I was getting almost daily alerts for 60 days for different rows of data and then they suddenly stopped. I have re-created the alert again and the new alert is working as intended, I will have to monitor to see if this suddenly stops triggering again. I wonder if this is something to do with the Fabric trial license.The History tab in Activator shows no activations, even when I adjust the time range back 2 months. The "send me a test action" is also greyed out. I wonder if this is something to do with the Fabric trial license? Although it still says we have 10 days left.
- burakkaragoz
Super User
Hi _Amy_ ,
Anusha66 hit the nail on the head regarding the logic, but since you are on a Fabric Trial and dealing with cross-workspace artifacts, there is another layer of complexity here.
Here are the three likely culprits for this "worked then stopped" behavior:
1. The "State" Trap (Most Likely) As Anusha mentioned, the condition "Increases to or above" is a state-change trigger.
Scenario: Day 1, value is 0.75. Day 2, value is 0.85. -> Alert Fires.
Scenario: Day 3, value is 0.86. -> No Alert.
Why: The system sees that the value is already in the "High" state. It needs to drop below 0.8 and come back up to trigger a new event with that specific logic.
Fix: If you want an email every time the data refreshes and stays high, you might need to change the logic, though that can get spammy.
2. The Fabric Trial "Sleep" Mode Fabric Trial capacities are notorious for pausing automatically if no interactive usage is detected for a while.
Since Activator runs in the background, it might not be enough to keep the Trial capacity "awake."
Check: Go to the Workspace settings where the Activator lives. Check the "Capacity" status. If the capacity is paused, the Activator service suspends all monitoring.
3. Dataset Refresh Dependency Activator on Power BI reports is not "Real-Time" in the strict sense. It checks data after a dataset refresh completes.
If your Power BI dataset (in the other workspace) failed to refresh or hasn't refreshed recently, Activator sees no "new" event to process.
Ensure the underlying dataset is on a Scheduled Refresh plan that is actually succeeding.
My Suggestion: Check the History tab in Activator again. If you see "No activations," it means the system thinks the condition hasn't been met (The State Trap). If the History is completely blank/stalled, check if your Trial Capacity is active.
Hope this helps you isolate the ghost!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.- _Amy_
Thanks for your reply, appreciate those suggestions.
In terms of (1) - the report has many rows of data in it, I only want an alert where a row increases (for example) from 0.75 to 0.85. I was getting almost daily alerts for 60 days for different rows of data and then they suddenly stopped. I have re-created the alert again and the new alert is working as intended, I will have to monitor to see if this suddenly stops triggering again. I wonder if this is something to do with the Fabric trial license.In terms of (2), I'm not able to see the Capacity status. I might need IT department to assist with this.
In terms of (3), the semantic model is on a daily scheduled refresh and is refreshing.
The History tab in Activator shows no activations, even when I adjust the time range back 2 months. The "send me a test action" is also greyed out.
- v-prasare
Community Support
Hi _Amy_,Based on what you’ve shared, this behavior usually occurs when the Activator service gets paused, something that happens quite often with Fabric Trial capacities. Since you recreated the alert and it worked briefly before stopping again, that strongly suggests the trial capacity may be going into sleep mode rather than there being an issue with your alert logic or the dataset refresh itself.Ask your admin/IT team to check the Trial capacity status and confirm that it’s activeThanks,Prashanth Are - v-prasare
Hi _Amy_,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support - v-prasare
Hi @_Amy_,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
