When your release requires changes
What the Requires Changes status means, where to see the requested fixes, and how to resubmit the release.
If review finds something to fix, the release comes back to you in the Requires Changes status.
How you find out
- You get an email notification with the summary and the detail of the changes.
- A banner appears on the release: "⚠️ This release requires changes before continuing", with View Detailed Changes and Edit and Fix Release.
- There's also a Required Changes tab with the full explanation.
What to do
- Read all the listed changes, not just the first one.
- Open the release to edit and make the corrections.
- Check that all the checks are green again in the Review → Summary tab.
- Click Resubmit for Review.
When you resubmit, the system runs the whole checklist again. The button stays disabled if any check fails.
Returning to Draft
From Requires Changes you can also use Return to Draft if you'd rather set the release aside and pick it up later. You don't lose anything; it just leaves the review queue until you resubmit.
Remember to resubmit
Saving your changes does not submit them. You'll see a reminder: "Changes applied — remember to Resubmit for Review". Until you click Resubmit for Review, the release stays in Requires Changes.
Was this article helpful?
Thanks for your feedback!
Related articles
The six release statuses in detail: what each one means, whether you can edit it, and what happens next.
How the Submit for Review button works, which requirements must be met, and what gets locked when you submit.
What the review timeline depends on, how the recommended minimum date is calculated, and what happens if you pick a date too soon.