Notification Logs

Debug why a push/email/SMS did or didn’t send, see provider responses, and filter by event or user.

Notification logs help you:

• Verify which push/email/SMS notifications were triggered.
• See why a notification wasn’t sent (preferences, mute/DND, missing token).
• Inspect provider responses to spot delivery patterns or failures.

Turn logging on

• In the CometChat Dashboard, go to Notifications → Logs and enable logging.
• Logging stays active for 7 days, then auto-disables. Re-enable it any time.

Retention timeline

Logs are kept for up to 14 days: 7 days while logging is active, plus 7 days after it stops. After that, they are permanently deleted.

Coverage

• Push providers: FCM, APNs, and custom providers.
• Email providers: SendGrid and custom providers.
• SMS providers: Twilio and custom providers.
• Events: Push covers messages/replies (1:1 and group), edits/deletes/reactions, and group membership events. Email/SMS cover messages and replies (1:1 and group).

Access and filtering

• Dashboard: Browse recent logs and narrow them down using any of the following filters:
  • Channel — push, email, or SMS.
  • Event — message sent, edited, deleted, reaction, group membership change, etc.
  • Sender (User) — filter by the UID that triggered the notification.
  • Receiver Type — user (one-on-one) or group.
  • Receiver ID — the UID or GUID that should receive the notification.
  • Status — sent, failed, skipped, etc.
• API: Use the Get logs API with query parameters (event, medium, receiver, status, time window, provider) for deeper filtering. See the API explorer for the full list.

Receiver ID filter requires Receiver Type. When filtering by Receiver ID in the dashboard, first select a Receiver Type (user or group), then enter the Receiver ID. Using Receiver ID without selecting Receiver Type first will not return results. We are tracking this requirement and plan to make Receiver ID work standalone in a future release.