Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
Paused event configurations in Real-Time hub
When you configure a consumer (such as an Activator alert or eventstream) to receive Azure or Fabric events through Real-Time hub, the configuration can enter a Paused state if the system detects a condition that prevents event delivery.
Discovering paused configurations
To check the status of event configurations:
- In Microsoft Fabric, select Real-Time on the left navigation bar.
- Select the Fabric events page or the Azure events page.
- Select the event group that you're interested in to see all the consumers for that event group.
- The Status column shows Active or Paused for each consumer.
- To see the specific reason for a paused state, select the ellipsis (...) on the line item to open the list of actions, and then select View details. The details pane shows a Reason field that explains exactly why the configuration is paused.
Reasons and mitigation
The following table lists the reasons a configuration can be paused and the steps to resolve each one.
| Reason | Description | Mitigation |
|---|---|---|
| Event ingestion is paused because the owner doesn't have sufficient permissions. | The owner of the event configuration has lost the subscribe permission on the source item. Permissions are assessed both during creation and for the lifetime of the event configuration. | Delete and recreate the configuration with a user that has sufficient subscribe permissions. For details on required permissions per event type, see Subscribe permissions for Azure and Fabric events. |
| Event ingestion is paused because the network configuration for source workspace blocks events to destination workspace. | The source workspace (the workspace where the events originate) has workspace-level private links configured to block public access, and there's no private link established from the consumer's network to the source workspace. | Allow public access on the source workspace, or establish a private link from the consumer's network to the source workspace, then delete and recreate the consumer configuration. For more information, see Private links for Azure and Fabric Events. |
| The owner of the event configuration is no longer available. | The user account that owns the event configuration has been deleted or disabled. | Delete and recreate the configuration with an active user that has sufficient permissions. |
Note
For tenant-level private links, when the Block Public Internet Access setting is enabled, Azure events (such as Azure Blob Storage events) aren't paused — the events are dropped at the Azure source and never reach Fabric. To discover dropped events in this scenario, investigate the metrics and diagnostic logs for the Azure resource (such as the Azure Storage account) in the Azure portal. For more information, see Private links for Azure and Fabric Events.
Related content
Feedback
Was this page helpful?