Failed push notification messages

Push notification delivery might fail for a number of reasons. You can view which messages failed and re-queue them to be sent out if necessary.

Before you begin

Role required: admin

About this task

Note: There is no way for the instance to guarantee or confirm push message delivery. See the iOS developer library for more information about how Apple handles push notifications.

Messages can also fail to send for several reasons, such as a large message queue or other issue with the instance. You can use a system property to control how long the instance queues a push notification after it is triggered.

Push notification message payload size is limited by provider:
  • Apple iOS: 2,048 bytes
  • Google: 4,096 bytes
Your instance does not send push messages that exceed this limitation. System logs save any failed messages. See the iOS Developer Library payload documentation for more information on Apple payload limitations.

Procedure

  1. Navigate to System Logs > Push Notifications.
    By default, the messages that were created today appear. You can change the filter if necessary. The Type column can have these values:
    • failure: The message could not be sent.
    • pending: The message is queued and will be processed.
    • success: The message was successfully sent, although not necessarily received by the mobile device.
  2. Put any failed messages back into the queue to be resent by selecting the check boxes next to the failed messages, and then selecting Re-queue failed push notifications from the choice list.
  3. If a number of push notifications continue to fail, consider increasing the value in the glide.push.notification.ttl_seconds property. See Push notification properties for more information.