Events & diagnostics

Inspect channel, API, and webhook events with message-first summaries and filters.

Last updated:

Use Control Centre → Events & diagnostics to inspect channel, API (application programming interface), and webhook events with message-first summaries. It is the first place to look when you need to understand what a channel actually did, or why something did not happen.

Columns

  • Time: when the event was recorded
  • Channel: the channel the event belongs to
  • Event: a message-first summary of what happened
  • Source: where the event originated (for example a sync job or an inbound webhook)
  • Entity: the record the event relates to
  • Message: the detail line
  • Type: the event category

On narrower layouts, the Event summary cell carries the hidden Type badge, and only the final Actions column stays sticky.

Filtering

Filter by channel, type, and date range (the default is All time), then open a full event record when you need the complete payload. Use Full events log to page through the full history.

When to use it

Use Events & diagnostics when:

  • A channel card reports a recent issue.
  • A sync, publish, or webhook did not produce the expected result.
  • You need to confirm whether a channel action reached ChannelWeave.
  • You want to compare a visible error with the underlying event timeline.

The list is message-first so most triage can happen from the row summary. Open a full event only when the summary is not enough.

Safe handling

Event details may contain operational identifiers and channel messages. Share screenshots carefully, and avoid pasting credentials or private buyer details into external support tools.