Dismiss events
Dismiss an event when it is dealt with, so that the feed and the Active events count show only what still needs attention.
You need: the admin or member role. Viewers see the buttons greyed out. Dismissing is available on every plan.
Dismiss one event
Section titled “Dismiss one event”- Open Dashboard and scroll to Real-time events. Check that the chip beside the title reads Connected.
- Find the event. Use Search event types… or the tenant drop-down if the feed is long.
- Optionally choose View and read Event Details first.
- Choose Dismiss on the row, or Dismiss Event in Event Details. There is no confirmation.
When it worked: the row disappears. There is no success message. The row also disappears for everyone else in the workspace, and Active events goes down by one.
Clear the feed with Dismiss All
Section titled “Clear the feed with Dismiss All”Dismiss All dismisses every event that is loaded in the feed, on every page.
- Open Dashboard and scroll to Real-time events.
- Decide the scope first. To clear one tenant or one period only, choose the tenant in the tenant drop-down, or set From and To. These limit which past events are loaded.
- Remember that the search box and Flagged only do not limit what is dismissed. Events that they hide are dismissed too.
- To load more events, raise History, up to 1000.
- Choose Dismiss All in the table footer.
- Read the dialog Dismiss all {N} events? and check the number. This is the number that will be dismissed.
- Choose Dismiss all. Choose Cancel to stop.
When it worked: the feed empties and there is no message. The tenant cards return to All clear.
If events remain, or the feed fills again with older events, more events were active than History loads. Repeat from step 5.
What happens afterwards
Section titled “What happens afterwards”- The event leaves the feed of every user in the workspace, straight away. It does not come back when you reload.
- The event is not deleted. It is stored as dismissed, with the email address of the person who dismissed it and the time, until event retention removes it.
- No screen in Identiguard shows dismissed events.
- Active events goes down. Total Tracked Events stays the same.
- The tenant card returns to All clear when its last active event is dismissed.
- Avg dismissal time, when the workspace has that card, includes the time this event waited.
- An incident that contains the event stays open. Close incidents on the Incidents page. See Manage incidents.
- Raising a ticket does not dismiss an event, and dismissing an event does not raise a ticket.
More detail is in Events.
If it does not work
Section titled “If it does not work”| What you see | Why | What to do |
|---|---|---|
| The Dismiss buttons are greyed out | You are a viewer, or another dismissal is in progress | Wait a moment. If you are a viewer, ask an admin for the member role. |
| Your role does not allow dismissing events. Contact an admin for help. | You are a viewer | Ask an admin for the member role |
| Cannot dismiss event: Connection not active. | The live connection is not open. Okta and Auth0 events need it. | Wait for the chip to read Connected, then try again. See Fix a feed that is not live. |
| Cannot dismiss event: event not found. | Someone else already dismissed it | Nothing |
| Failed to dismiss Entra event: {message} | The request for an Entra ID event failed, often because of too many requests | Wait a minute and try again |
| Dismiss All is greyed out | The filtered list is empty, you are a viewer, or a dismissal is in progress | Clear the filters, or wait |
| No events to dismiss. | Nothing is loaded in the feed | Nothing |
| Dismissed {n} events. {m} failed. | Some events were not dismissed | Check the chip reads Connected, then choose Dismiss All again. The events that failed are still on screen. |
| Dismissed {n} events. {m} left - too many requests, try again in a minute. | Entra ID events reached the rate limit | Wait a minute, then choose Dismiss All again |
| You dismissed the wrong event | There is no undo | Find the event in the provider’s own log. If the record must be recovered, raise it with the product team. |
The full list of messages is in Events: troubleshooting.