Contents Now Platform Capabilities Previous Topic Next Topic Requeue failed push notification messages Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Requeue failed push notification messages Push notification delivery might fail for various reasons. You can view which messages failed and requeue them to be sent out if necessary. Before you beginRole required: admin About this task Note: There is no way for the instance to guarantee or confirm push message delivery. For more information on how Apple handles push notifications, see the Local and Remote Notification Programming Guide for Apple developers. 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. For details on Apple payload limitations, see the Local and Remote Notification Programming Guide for Apple developers. Procedure 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 for processing. success: The message was successfully sent, although not necessarily received by the mobile device. 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. If some push notifications continue to fail, consider increasing the value in the glide.push.notification.ttl_seconds property. See Push notification properties for more information. Related tasksActivate push notificationsRelated conceptsPush notification retentionRelated referencePush notification systemInstalled with push notificationsPush notification propertiesPush notification setup with the ServiceNow mobile applicationPush notification setup with a custom push application On this page Send Feedback Previous Topic Next Topic
Requeue failed push notification messages Push notification delivery might fail for various reasons. You can view which messages failed and requeue them to be sent out if necessary. Before you beginRole required: admin About this task Note: There is no way for the instance to guarantee or confirm push message delivery. For more information on how Apple handles push notifications, see the Local and Remote Notification Programming Guide for Apple developers. 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. For details on Apple payload limitations, see the Local and Remote Notification Programming Guide for Apple developers. Procedure 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 for processing. success: The message was successfully sent, although not necessarily received by the mobile device. 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. If some push notifications continue to fail, consider increasing the value in the glide.push.notification.ttl_seconds property. See Push notification properties for more information. Related tasksActivate push notificationsRelated conceptsPush notification retentionRelated referencePush notification systemInstalled with push notificationsPush notification propertiesPush notification setup with the ServiceNow mobile applicationPush notification setup with a custom push application
Requeue failed push notification messages Push notification delivery might fail for various reasons. You can view which messages failed and requeue them to be sent out if necessary. Before you beginRole required: admin About this task Note: There is no way for the instance to guarantee or confirm push message delivery. For more information on how Apple handles push notifications, see the Local and Remote Notification Programming Guide for Apple developers. 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. For details on Apple payload limitations, see the Local and Remote Notification Programming Guide for Apple developers. Procedure 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 for processing. success: The message was successfully sent, although not necessarily received by the mobile device. 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. If some push notifications continue to fail, consider increasing the value in the glide.push.notification.ttl_seconds property. See Push notification properties for more information. Related tasksActivate push notificationsRelated conceptsPush notification retentionRelated referencePush notification systemInstalled with push notificationsPush notification propertiesPush notification setup with the ServiceNow mobile applicationPush notification setup with a custom push application
