All Products
Search

This Product

    Mobile Platform as a Service:Manage multiple push messages

    Document Center

    Mobile Platform as a Service:Manage multiple push messages

    Last Updated:Jun 10, 2026

    Message Push Service (MPS) provides real-time statistics on batch push and broadcast push tasks—whether created in the mPaaS console or triggered via API—so you can track delivery status across all your campaigns.

    View push tasks

    1. Log in to the mPaaS console, select your app, and go to Message Push Service > Message management > Multiple push records.

    2. In the search box in the upper-right corner, enter a task ID or task name, and set a time range to filter results. Matching tasks appear in the task list, sorted by creation time in descending order.

      Each task in the list shows the following information:

      • Task ID: The unique identifier assigned to the push task by the system.

      • Task name (API): For tasks created in the mPaaS console, the system generates a name in the format "console + timestamp" (for example, Console Wed Mar 24 14:47:23 CST 2021). For tasks triggered via API, the name is whatever the caller specified.

      • Push type: Indicates whether the message was sent as an immediate push or a scheduled push.

    3. To view delivery details for a task, click the Expand button (+) next to it. The following metrics are shown:

      • Pushed messages: Total number of messages dispatched by the MPS backend (counted by the backend).

      • Successfully pushed messages: Total number of messages the MPS backend successfully delivered to the next hop (counted by the backend).

      • Messages delivered: Number of messages confirmed as received on the device. For Apple Push Notification service (APNs) (iOS channel) and Android third-party channels (such as Xiaomi and Huawei), the count is based on delivery receipts from the respective vendor backends. For the Android self-maintained channel, the count is based on client-side tracking reports.

      • Time to live (TTL): How long MPS attempts to deliver the message. Within this window, MPS retries delivery whenever the target device reconnects or the user completes device registration. Once the TTL expires, MPS stops attempting delivery.

    Revoke messages

    Revoking a message stops delivery to devices that have not yet received it. What happens to messages already on a device depends on the message type. You can revoke messages pushed within the past 7 days. For details, see Message revocation.

    • Silent notifications: Withdrawn immediately. Users on the client side are unaware of the revocation.

    • Notification messages: MPS stops pushing to devices that have not yet received the message, and cancels display of messages that have arrived on a device but not yet appeared on screen.

      Note

      Messages with a Failed delivery status cannot be revoked.