docs(data-retention): warn that enabling ZDR is a breaking change - #155
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Call out upload and polling restrictions before customers enable zero data retention, with a short migration checklist. Co-authored-by: Cursor <cursoragent@cursor.com>
mfernandez-gladia
force-pushed
the
docs/zdr-breaking-change-warning
branch
from
October 2, 2026 08:33
47d1a53 to
8ca85c9
Compare
clemos
approved these changes
Oct 2, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/v2/uploadand pollingGET /v2/pre-recorded/:id) that lived on stale PR Update ZDR doc #123 but never reachedmainaudio_url+ callback + drop polling)Test plan
/v2/upload,GET /v2/pre-recorded/:id,POST /v2/pre-recorded, and callback success docs