Fabric Business Events: what delivery guarantees and replay pattern should we design for?
Hi all, I am testing the newer Business Events capability in Fabric Real-Time Intelligence and trying to understand what reliability assumptions should be made for a production design. The pattern I am looking at is roughly: Eventstream → Business Event → Activator → downstream action / User Data Function with Eventhouse enabled so the published business events are also retained for historical analysis. The current documentation explains the publisher/consumer model and shows how Eventstream can publish a governed business event that Activator then consumes. What I have not been able to find clearly documented is the delivery contract between the published business event and its consumers. A few things I am trying to clarify: If an Activator consumer or downstream action is temporarily unavailable, does Fabric retry delivery of the business event? Should consumers assume at-least-once delivery and therefore be designed to handle duplicate events, or is a different delivery model used? Is event ordering guaranteed in any scope, for example for events from the same Eventstream publisher? Since published business events can also be retained automatically in Eventhouse, is that retained history intended to support replay/reprocessing after a consumer outage, or is it primarily an analytical record and replay would need to be implemented separately? Are there documented retry or delivery-retention windows that should be considered when designing an operational workflow? I am mainly trying to understand what a resilient production pattern should look like when the business event triggers something with side effects, where processing the same event twice or silently missing an event would matter. Would you generally make the downstream consumer idempotent and treat Eventhouse as an audit/recovery store, or is there a more Fabric-native pattern for this? Interested to hear how others are approaching this with Business Events and Activator.Microsoft Fabric Activator generating repeated false alerts despite stable Power BI metric
Hi! I'm experiencing an issue with Microsoft Fabric Activator that started last week after working reliably for several months. I have several Activator alerts monitoring Power BI metrics that indicate whether data for the previous day is available. After the daily semantic model refresh, the metric correctly changes from FALSE (0) to TRUE (1) once yesterday's data is available. The problem is that after the refresh has completed, the report/dashboard remains stable, but Activator continues to fire the alerts repeatedly. What I observe The semantic model refreshes successfully. The Power BI report/dashboard correctly shows TRUE (or 1) and does not change afterwards. The semantic model is not refreshed again for several hours. However, the Activator PowerBI Metric live feed repeatedly alternates between TRUE/FALSE (or 1/0) for some monitored objects, even though the report values remain unchanged. Since my alert is configured as "Changes to TRUE", these false state changes cause repeated alert notifications. Expected behaviour The semantic model refreshes. The metric changes from FALSE to TRUE once. Activator triggers a single alert. No further alerts are generated until the metric actually changes again. Actual behaviour The semantic model refreshes successfully. The report/dashboard values remain stable. The Activator PowerBI Metric live feed shows alternating TRUE/FALSE (or 1/0) values. Alerts continue to fire despite no changes to the underlying data. Troubleshooting performed Confirmed the semantic model had not refreshed again. Confirmed the report/dashboard values remained unchanged. Confirmed the alert definition had not been modified. Deleted and recreated the Activator alerts. Replaced numeric 1/0 measures with Boolean TRUE/FALSE measures. The issue persists after all of the above. Has anyone else experienced similar behaviour recently? Is this a known issue with Fabric Activator or the PowerBI Metric event source? Thanks in advance!
Activator Not Showing in My Workspace
According to the Fabric Capacity Metrics, an Activator item is consuming a high amount of capacity units. However, when I check the workspace manually, no Activator item is visible. I wanted to delete or remove this item, as it appears to have been activated by mistake.
