What you receive

Updated 1 October 2026 · BugsRadar team

One rule: a full message while your channel keeps up, a bundle when it can't. While an error repeats, its message keeps the count. A message about one error starts with the project name and, under it, the level: Critical, Error, Warning or Information. The samples below are from Telegram. Discord gets the same content; Pushover, a short push notification, comes without the stack trace.

The first occurrence

A new error arrives at once: the project, the level, the exception and its message, where it happened, the environment, host, version and time, the event's properties and the stack trace.

at Shop.Payments.PaymentService.ChargeAsync(Order order)
at Shop.Orders.OrderService.CreateOrder(Int32 orderId)

Repeats

While the error keeps happening, its repeats are counted. In Telegram and Discord the count is written into the message of the first occurrence, without a new notification: the message is updated 10 minutes after it was sent, the next time after 30 minutes, then after an hour, then every 6 hours. When a window passes without repeats, the error is closed, and its next occurrence arrives as a new first message.

at Shop.Payments.PaymentService.ChargeAsync(Order order)
at Shop.Orders.OrderService.CreateOrder(Int32 orderId)

Pushover can't edit a message, so there the repeats arrive as summaries at the same moments. The same happens in Telegram and Discord when you turn Live count off for a channel on the Channels page: each summary is then a new message with its own notification.

Bundles

When your channel can't keep up - errors have been waiting in its queue, the service asked for a pause, or a project has sent many messages within the hour - BugsRadar bundles the waiting errors into one message: a line per error with its type, place and count, grouped by project, without stack traces.

Which channels an error goes to is decided by rules; what a channel needs is on the Channels page.