Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Once the configuration is completed and when the push notification is triggered, the following sequence occurs:

  1. The alerts will be temporarily stored in the CT_ALERT_PUSH_NOTIF_PENDING table as pending alerts.


  1. The pending alerts will be checked by the delivery scheduler and sent to FCM via the FCM communicator. The FCM communicator converts the alerts as JSON string before sending those to the FCM.


  1. Once the alerts reach the FCM, the alerts will be validated for the tokens and API keys. If the validation is successful, the alerts will be sent to the user device as push notifications. If the validation is unsuccessful, then the relevant error message will be thrown to the app by FCM.


  1. The entries of the alerts that have been successfully sent to the user device will be moved from the CT_ALERT_PUSH_NOTIF_PENDING table to the CT_ALERT_PUSH_NOTIF_PENDING_HB table. The alerts that are in pending or failed validation status will be retained in the CT_ALERT_PUSH_NOTIF_PENDING table. The delivery scheduler will keep checking for the pending or failed alerts until their validation is successful.
  • No labels