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

[Akshay3071]

Hi,

I am currently working with Microsoft Fabric Activator, where I have configured an alert on a KQL function output from an Eventhouse datasource. The alert is designed to trigger every 10 minutes, based on a change detection condition on a computed column (AlertTriggerKey) that increments on every 10-minute window.

Observed Behavior

Activator is detecting the condition and recording each trigger correctly in the alert history, confirming that the rule evaluation and condition matching are functioning as expected. However, the email delivery cadence is inconsistent and does not align with the expected 10-minute interval.

Specifically, the pattern I am observing is inconsistent and does not follow a fixed delay. While some alerts are delivered on time, others arrive with unpredictable delays ranging from 30 minutes to over an hour, and certain alerts are missed entirely with no corresponding email delivery whatsoever. There is no consistent gap between the expected trigger time and the actual email delivery time — the delay varies arbitrarily across alerts and some triggers recorded in Activator history have no corresponding email delivered at all, making it impossible to rely on the notifications for real-time operational decisions.

What Has Been Verified

•  Rule configuration is correct
•  Trigger condition (AlertTriggerKey → Changes) is working as expected
•  Activator history confirms alerts are being recorded at the correct 10-minute intervals
•  Throttle limit is not being hit — only 6 alerts per hour
•  Recipients and action configuration are correctly set up
•  Emails are not being filtered into spam or junk

Core Issue

The alert history and the email delivery are out of sync. Activator is recording the trigger at the correct cadence, but the email notifications are being delivered with delays and in some cases are dropped entirely, suggesting the issue lies specifically in the email dispatch pipeline, not in the rule evaluation or condition detection layer.

Has anyone encountered a similar pattern where Activator history is accurate but email delivery is inconsistently delayed or completely missing? Is there a known latency issue or queuing behavior in the Fabric Activator email dispatch system that could explain this? Any guidance or workaround would be greatly appreciated.

Thank you.

[v-veshwara-msft]

Hi @Akshay3071 ,

We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.

[v-veshwara-msft · Accepted solution]

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.

[v-veshwara-msft]

Hi @Akshay3071 ,

Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.