Activator Email Delivery Inconsistent — Alerts Recorded in History but Emails Delayed and Missing

Hi Akshay3071 ,

Thanks for reaching out to the Microsoft Fabric Community, and thank you for the detailed explanation.

From the information shared, it appears that the rule evaluation itself is functioning as expected, since Activator history is recording the alerts correctly at the configured intervals. This helps narrow the scope, as the issue seems to be occurring at the notification delivery stage rather than at the condition detection stage. You can refer to the common error codes and delivery failure scenarios covered here for reference: Troubleshooting errors in Activator - Microsoft Fabric | Microsoft Learn

Since you've already validated the rule configuration, trigger conditions, throttling frequency, recipient settings, and spam filtering, another area worth reviewing would be the Fabric Capacity Metrics app around the timestamps where delayed or missing notifications occurred.

Under prolonged capacity pressure, Activator may continue evaluating rules and recording history successfully while certain background operations can experience delays. This could potentially contribute to notification delivery latency in some scenarios. Additional details regarding Activator throttling behavior can be found here:

Activator throttling effects - Microsoft Fabric | Microsoft Learn

I also found a few threads where similar behavior has been reported -- alert actions appearing correctly in Activator history but notifications delayed or not delivered consistently. These may help for comparison with your scenario:

Solved: Power Bi alert showing Actions but no message deli... - Microsoft Fabric Community

Delayed alert from Power BI to Teams - Fabric Acti... - Microsoft Fabric Community

As an additional troubleshooting step, if near real-time notification reliability is critical for your use case, you may also consider testing a Power Automate custom action instead of the native email action -- details here:

Use Custom Actions to Trigger Power Automate Flows - Microsoft Fabric | Microsoft Learn.

This provides independent run history and retry behavior, which can help isolate whether the behavior is specific to the notification delivery pipeline. 

Please let us know if you observe any capacity spikes or additional patterns around the timestamps of the missed notifications.

Thank you.