> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypersender.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Message Push Failed

> Sent when Hypersender could not push a message to the phone.

Event: `message.notification.failed`

Sent when Hypersender could not push a message to the phone, so the phone never got it. `status` is `failed`. Common `failure_reason` values:

* `Max send attempts reached`: every attempt allowed by `max_send_attempts` failed.
* `Phone does not have an FCM token. Open the Android app to register push notifications.`: the phone is not registered for push notifications. Open the app on the phone so it registers again.
* `MAX_ATTEMPTS`: the send job gave up before the message reached the phone.
* `Message expired`: the message expired before it could be pushed to the phone. In this case `status` is `failed`, not `expired`.

Hypersender retries the push while attempts remain, so you can get this event more than once for the same message. Check `send_attempt_count` and `max_send_attempts`.

See [Failure reasons](https://docs.hypersender.com/v2/api-reference/sms/sms-api-introduction.md#failure-reasons) for the full list.


## OpenAPI

````yaml v2/api-reference/sms-webhooks/sms-webhooks.json webhook message-notification-failed
openapi: 3.1.0
info:
  title: Hypersender SMS Webhooks
  description: >-
    Hypersender sends a `POST` with a JSON body `{event, data}` to your webhook
    URL for the SMS events you pick in the dashboard.


    If you set an Authorization Secret on the webhook, it is sent in the
    `Authorization` header. Hypersender does not sign SMS webhooks.
  version: 1.0.0
servers: []
security: []
paths: {}

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.