Skip to content

Commit 2005a2b

Browse files
authored
Update change-notifications-lifecycle-events.md
1 parent d329c85 commit 2005a2b

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

concepts/change-notifications-lifecycle-events.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,10 @@ The following steps represent the flow of an authorization challenge for an acti
160160
1. Acknowledge receipt of the lifecycle notification by responding to the POST call with `202 - Accepted` response code.
161161
2. Validate the authenticity of the lifecycle notification.
162162
3. Ensure that the app has a valid access token to take the next step.
163-
4. Call either of the following two APIs. If the API call succeeds, the change notification flow resumes.
163+
4. Call *either* of the following two APIs. If the API call succeeds, the change notification flow resumes.
164+
165+
> [!IMPORTANT]
166+
> Don't issue a reauthorize request (`POST /subscriptions/{id}/reauthorize`) and an update request (`PATCH /subscriptions/{id}`) for the same subscription within a 10-minute window. Sending these requests concurrently or in rapid succession can result in subscription state inconsistencies. If you need to reauthorize and renew a subscription, use a single PATCH request with an updated **expirationDateTime**, which performs both actions in one operation.
164167
165168
- Call the `/reauthorize` action to reauthorize the subscription without extending its expiration date.
166169

@@ -191,9 +194,6 @@ The following steps represent the flow of an authorization challenge for an acti
191194
192195
You might retry these actions later, at any time, and succeed if the conditions of access change.
193196
194-
> [!IMPORTANT]
195-
> Do not issue a reauthorize request (`POST /subscriptions/{id}/reauthorize`) and an update request (`PATCH /subscriptions/{id}`) for the same subscription within a 10-minute window. Sending both requests concurrently or in rapid succession can result in subscription state inconsistencies. If you need to both reauthorize and renew a subscription, use a single `PATCH` request with an updated `expirationDateTime`, which reauthorizes and renews the subscription in one operation.
196-
197197
### Additional information
198198
199199
- Authorization challenges don't replace the need to renew a subscription before it expires.

0 commit comments

Comments
 (0)