# Webhook Logs > Every event Meta has sent about your WhatsApp number - statuses, filters, charts, payload details, and what to do about failed events. Source: https://docs.theavoxai.com/logs Logs is the record behind everything else in your dashboard. Every event Meta sends Avox about your WhatsApp number - a new message, a delivery receipt, a template decision, a call - is logged here with its processing status. The header reads "Webhook delivery history for your account." > **Note** > > Logs shows what Meta sends to Avox. Requests your own server makes with an API key, and messages Avox > forwards to your endpoint, are on [API logs](https://docs.theavoxai.com/connections/api-keys#api-logs). ## Who can use Logs Every member of the Switchboard - Admins and Managers - can view Logs and open any event. Logs is read-only. Logs needs a connected WhatsApp number. Until one is connected, the **Logs** item in the sidebar shows a lock with "This feature needs a WhatsApp connection first." ([AVX-3001](https://docs.theavoxai.com/error-codes/avx-3001)). ## How an event moves through Avox When Meta sends an event, Avox confirms it really came from Meta, stores it right away, and then processes it - adding the message to your [Inbox](https://docs.theavoxai.com/inbox), updating a template's status, logging a call, and so on. See [Reliability](https://docs.theavoxai.com/reliability) for the full picture. Each event has one of four statuses: | Status | Meaning | | --- | --- | | `pending` | Received and waiting to be processed. Events normally move on within seconds. | | `processing` | Being processed right now. | | `processed` | Done. Its effect is visible in your dashboard. | | `failed` | Avox tried 5 times and couldn't process it. The **Error** column says why. | If processing an event fails, Avox puts it back in line and tries again automatically. The **Attempts** column counts the tries. After the fifth try the event is marked `failed`. ## Choosing a range The `7d`, `30d`, and `90d` buttons at the top choose which events the charts, table, and insights cover. Logs opens on `30d`, and changing the range takes you back to the first page of the table. ## Charts - **Delivery status** - how many events in the range are processed, pending, processing, and failed. - **Top event types** - the event types Meta sent most in the range (up to six). A sudden new entry is often the first sign of a new setting or integration on your WhatsApp account. With no events in the range, both read "No webhook activity in this window yet." ## Filters Two filters sit above the table. They work together with the range, so you can, for example, list only failed template updates from the last 7 days. - **Status** - **All statuses**, `pending`, `processing`, `processed`, or `failed`. - **Event type** - **All event types** or one of the types below. | Event type | What it is | | --- | --- | | `messages` | A customer message, or a sent / delivered / read / failed update for a message you sent. | | `message_template_status_update` | Meta approved, rejected, paused, or disabled one of your templates. | | `phone_number_quality_update` | Your number's quality or messaging limit changed. Shows in Health's Quality history. | | `calls` | A WhatsApp call event, such as connect or terminate. | | `history` | Chat history imported from the WhatsApp Business app. | | `smb_app_state_sync` | Contacts synced from the WhatsApp Business app. | | `smb_message_echoes` | A message your team sent from the WhatsApp Business app. | | `account_alerts` | An alert Meta raised about your account. | | `account_update` | A change Meta made to your account, such as a review decision. | | `automation_skipped` | Created by Avox, not Meta: an automation didn't run because the connection was paused after the subscription was canceled. | For each of Meta's event types in detail, with example payloads, see [Meta webhooks](https://docs.theavoxai.com/whatsapp/webhooks). ## The events table | Column | What it shows | | --- | --- | | **Event** | The event type. | | **Status** | `pending`, `processing`, `processed`, or `failed` (in red). | | **Attempts** | How many times Avox has tried to process it. | | **Received** | When Avox received it. | | **Error** | Why the last attempt failed, or `-`. | The table shows 25 events per page, with "Page 1 of 8 ยท 190 events" and **Previous** / **Next** buttons when there are more. With no events at all it reads "No webhook activity logged yet."; with filters that match nothing, "No webhook events match those filters." ## Opening an event Click any row to open its details: - **The event type** as the title. - **When it was received**, and when it was processed - or "Not yet processed". - **The error**, in red, if the event failed. - **The full payload** - the exact JSON Meta sent, formatted for reading. The payload is the best starting point when you're investigating a delivery question or talking to [Support](https://docs.theavoxai.com/support): it shows exactly what Meta told Avox, and when. ## The Insights rail The **Insights** card on the right ("What's worth noticing right now") reads the range for you. The [Avox Avatar](https://docs.theavoxai.com/avox-avatar) at the top of the card is smug when all is well, unsure when something deserves a look, and sad when something needs attention. | Insight | When it appears | | --- | --- | | 12% of webhooks in this window failed to process - worth investigating soon. | 10% or more of the events in the range failed. (Critical) | | 3 webhooks failed to process in this window. | Some events failed, but under 10%. | | "messages" is your most common event type this window (120 received). | There's any activity in the range. | | No webhook activity in this window yet. | Nothing arrived in the range. | Under the card, **Learn more in the docs** opens this page. ## When events fail 1. Open the failed event and read its error. 2. Check the connection on [Health](https://docs.theavoxai.com/health) - a paused or disconnected number is the most common cause. 3. If the error isn't clear, or many events fail together, contact [Support](https://docs.theavoxai.com/support) with the event type and the time it was received. Avox staff can look at the event and process it again. ## How long logs are kept Events are kept for the log retention period set on [Compliance](https://docs.theavoxai.com/compliance), then removed automatically. ## Errors on this page If the log doesn't load, you see "Couldn't load your webhook logs. Try again." ([AVX-3079](https://docs.theavoxai.com/error-codes/avx-3079)). Refresh the page.