---
title: "What does the Google Play notification SUBSCRIPTION_PAUSE_SCHEDULE_CHANGED mean?"
description: "SUBSCRIPTION_PAUSE_SCHEDULE_CHANGED (11) means a customer scheduled or changed a pause. Access continues until the next renewal date; the pause starts then."
url: https://revenuedot.app/docs/notifications/google-subscription-pause-schedule-changed
---

# What does the Google Play notification SUBSCRIPTION_PAUSE_SCHEDULE_CHANGED mean?

The Google Play notification SUBSCRIPTION_PAUSE_SCHEDULE_CHANGED means a customer set or changed a pause that starts at the end of the current period.

## Quick facts

| | |
|---|---|
| Notification | `subscriptionNotification.notificationType` 11, `SUBSCRIPTION_PAUSE_SCHEDULE_CHANGED` |
| Where | Google Play real-time developer notifications (Pub/Sub, `DeveloperNotification`) |
| Sent by | Google Play, as a Cloud Pub/Sub push to your endpoint |
| What Google says | A subscription pause schedule has been changed. |

## What triggers it

- The customer chose to pause in Play. A pause takes effect only after the current billing period ends.
- The subscription is still `SUBSCRIPTION_STATE_ACTIVE` and `autoRenewEnabled` is true. The customer keeps access until the next renewal date.
- Pause lengths run from one week to three months depending on the recurrence.

## What your server should do

1. Do not trust the message for the state. Google says a notification only tells you the purchase state changed; call the Google Play Developer API (`purchases.subscriptionsv2.get`) with the purchase token to get the full state.
2. Keep access until the renewal date and show that a pause is coming.
3. When the pause starts, you get `SUBSCRIPTION_PAUSED`.
4. Offer a way to resume by deep link to Google Play.
5. Answer 2xx once you have handled the message, and skip a `messageId` you have seen: Google recommends checking the uniqueness of message IDs so a redelivery does not make a second API call.

## Example

```javascript
// A Pub/Sub push body: the notification is base64 JSON in message.data.
const body = { message: { messageId: "136969346945", data: Buffer.from(JSON.stringify({"version":"1.0","packageName":"com.example.app","eventTimeMillis":"1790800914000","subscriptionNotification":{"version":"1.0","notificationType":11,"purchaseToken":"PURCHASE_TOKEN"}})).toString("base64") } };

function decide(body) {
  const n = JSON.parse(Buffer.from(body.message.data, "base64").toString("utf8"));
  if (!(n.subscriptionNotification?.notificationType === 11)) return "ignore";
  return "keep access until the renewal date, show the coming pause";
}

console.log(decide(body));
```

*Run-checked: `npm run check:snippets` runs this snippet with Node and compares its output with `keep access until the renewal date` (checked 2026-10-03).*

## How RevenueDot handles it

RevenueDot answers every handled message with 2xx and every temporary failure with 5xx so Pub/Sub redelivers it. For subscription types it re-reads the subscription from Google with `purchases.subscriptionsv2.get` and applies that state, and it acknowledges a new purchase if the app has not. A purchase RevenueDot has not seen is applied only when the app's **Track new purchases from server-to-server notifications** setting is on. RevenueDot reads the scheduled resume time from the version 1 subscription API and stores it as the auto-resume date while the subscription is still active. A newly set resume date gives `SUBSCRIPTION_PAUSED` with `auto_resume_at_ms`, at scheduling time, while access continues.

## Related

- [What does the Google Play notification SUBSCRIPTION_PAUSED mean?](https://revenuedot.app/docs/notifications/google-subscription-paused.md)
- [What does the Google Play notification SUBSCRIPTION_RECOVERED mean?](https://revenuedot.app/docs/notifications/google-subscription-recovered.md)
- [What does the Google Play notification SUBSCRIPTION_CANCELED mean?](https://revenuedot.app/docs/notifications/google-subscription-canceled.md)
- [Which webhook events does RevenueDot send?](https://revenuedot.app/docs/api/webhook-events.md)
- [Set up Google Play notifications in RevenueDot](https://revenuedot.app/docs/guides/google-play.md)

## Source

- [Google: Real-time developer notifications reference guide](https://developer.android.com/google/play/billing/rtdn-reference)
- [Google: Subscription lifecycle](https://developer.android.com/google/play/billing/lifecycle/subscriptions)
- [RevenueDot server: stores/google/notifications.ts (how the message is received)](https://github.com/revenuedot/revenuedot/blob/main/apps/server/src/stores/google/notifications.ts)
- [RevenueDot server: stores/google/sync.ts (how the purchase is re-read and applied)](https://github.com/revenuedot/revenuedot/blob/main/apps/server/src/stores/google/sync.ts)
- [RevenueDot server: stores/google/map.ts (how Google's state becomes a stored purchase)](https://github.com/revenuedot/revenuedot/blob/main/apps/server/src/stores/google/map.ts)
- [RevenueDot core: events.ts (how a change becomes a webhook event)](https://github.com/revenuedot/revenuedot/blob/main/packages/core/src/events.ts)

Checked: 2026-10-03