Push Notification Engine Response Handling
MATRIXX Engine response handling for Apple Push Notification Service (APNs) and Firebase Cloud Messaging (FCM).
After the Notification Server sends the APNs or FCM formatted message to the APNs or FCM device platform, the Notification Server delivers a response back to MATRIXX Engine.
The possible responses sent to MATRIXX Engine are:
| Response Name | Response Description |
|---|---|
| STATUS_SUCCESS (0L) | The message was delivered successfully. |
| STATUS_FAILED (1L) | The message failed. This may result in another notification attempt by MATRIXX Engine. |
| STATUS_FILTERED (2L) | The message was not sent, but do not want to try again. |
When a subscriber has multiple valid tokens (the APNs or FCM formatted message contains multiple subscriber APNs or FCM tokens), the Notification Server sends a push notification to the APNs or FCM for each one, but MATRIXX Engine considers the push notification to be a single notification.
The successful delivery with at least one token is considered a STATUS_SUCCESS.
Where all tokens fail, this is considered STATUS_FILTERED, as no retry is done.
If the APNs or FCM device platform are unavailable, this is considered a STATUS_FAILED.
In the current release, if the APNs or FCM message response returns an Invalid Token response, the Notification Server route that handles the response does not coordinate the removal of the token from the subscriber’s token list (the token is not removed from the subscriber management (SubMan) database in MATRIXX Engine). To remove the token, customization of the Apache Camel configuration on the Notification Server is required.