Find the event that needs attention

3 minute read · Signals & Errors

Use the feed to find the event that explains a broken app flow. Unread attention and total stored history are different counts.

• Investigate a signal rather than just clearing a badge
• Share and manage attention
• Clear captured events deliberately
• Go from an event to a fix

Investigate a signal rather than just clearing a badge#

Select the intended Signal app, filter/search the event list and open an event's details. Compare its occurrence time with receipt time, environment and URL/method when available. For an exception, read the class, file/line and trace together. Multiple similar messages may be repeated occurrences rather than one event displayed twice.

Use the context to reproduce the failure in a safe development environment. After a fix, trigger the same path and verify the expected behavior. Marking an event seen updates attention state; it does not prove the application bug was repaired.

Share and manage attention#

Use the supported app sharing or join-code flow to grant the intended access. An ingestion token authorizes sending events and should not be treated as a general account credential. Joining a shared app does not grant another user's personal workspace or Vault access.

Configure OS alerts, sound and quiet hours to suit the work. Muting an app suppresses attention without erasing its history. Unread badges count unseen events, which is different from the total number stored. Use mark-one/all-seen when you have reviewed the appropriate scope.

Clear captured events deliberately#

Clear events only for the chosen app and category. Deleting a Signal app is a different action from dismissing a notification and should be deliberate. Retention must stay within the account/category boundary; an event burst should not remove projects, saved connections or mail from another category.

If notifications are missing, check the app's mute/quiet-hour settings and OS permission before changing ingestion configuration. If events themselves are absent, return to the integration guide. Redact traces and request context before exporting or sending evidence to an agent.

Go from an event to a fix#

Search/filter the relevant app and environment, then open an event's details. Compare when it occurred with when it was received. Read the exception, trace and request context, and correlate them with the action you can reproduce in Preview or the API client. Send only the necessary redacted context to the project conversation.

Mark an event seen after reviewing it; an unread badge is attention state, not the total number of stored events. Use notification, sound, mute and quiet-hour controls to decide when alerts interrupt you. Muting an app does not erase its history.

Sharing and join codes grant the access described by the app's controls; do not expose an ingestion token as a substitute for inviting a collaborator. Clear events deliberately when they are no longer needed, keeping any authorized evidence first. Deleting the Signal app also affects how the sending application can be monitored, so review that separately from clearing a badge.

Related guides: connect a sender, checking the app.