Skip to main content

Why am I seeing <unlabeled event> in Sentry?

Issue

Issues or events show the title <unlabeled event>, so I cannot tell what failed from the issue stream. I need to know why the title is missing and how to fix it.

Applies To

  • All SaaS Customers and Self-Hosted Users

  • Error Monitoring

  • SDK Setup

Resolution

<unlabeled event> is Sentry’s placeholder title when a default event has no usable message. Sentry sets that title when logentry has no formatted or message value. Error events that lack exception metadata use a different placeholder (<unknown>), not <unlabeled event>.

Common causes:

  1. Empty or missing message data (for example captureMessage(""), or a payload with no logentry message).

  2. Custom beforeSend logic that removes the message or strips exception data so the event no longer has a title. See filtering documentation.

  3. Manual SDK or API events that omit required fields. See capturing errors and messages.

  4. An outdated SDK sending incomplete event payloads.

Steps to fix:

  1. Open an affected event in Sentry. Check the event JSON for logentry / message and for any “error encountered while processing this event” notices.

  2. Search your codebase for empty captureMessage / captureException calls and for beforeSend that deletes event.message, event.logentry, or event.exception.

  3. Temporarily remove or no-op beforeSend. If titles return, restore scrubbing without clearing message or exception fields.

  4. Upgrade to the latest SDK version for your platform.

  5. After you fix the payload, new events get normal titles. Existing <unlabeled event> issues keep their old title unless new events update the issue.

If the event JSON still has no message after these steps, contact Sentry support.

Related Articles
Did this answer your question?