Seeing what looks like the same class of bug, but on a different resource. I tried removing a subscription group (and its two subscriptions) from an app version's review submission after a 2.3.2 rejection, planning to fix the promotional images and resubmit them separately. The UI shows them as "Removed," but clicking "Add for Review" on them now fails with "Something went wrong. Try again." Checking the network tab, the actual API response is: 409 STATE_ERROR.ENTITY_STATE_INVALID "subscriptionGroupVersions with id ... is not in valid state." associatedErrors: STATE_ERROR.ITEM_PART_OF_ANOTHER_SUBMISSION "subscriptionGroupVersions with id ... was already added to another reviewSubmission with id ..." The reviewSubmission ID it references is the same submission that originally got rejected and is now back in "Waiting for Review" after I resubmitted the app version alone. So it seems the backend still considers the subscriptionGroupVersion locked to that submission even though the UI shows it detached — same stuck-state pattern as this thread, just a different entity type. App Store Connect's own confirmation dialog when removing the item explicitly says "You'll need to resubmit this item to App Review in a different submission" — so this directly contradicts what the UI promises. Filed as FB25091991 in Feedback Assistant and also raised with Developer Support if anyone wants to reference it. Curious if this resolves once the parent submission reaches a terminal state, or if it needs Apple engineering to clear it like in your case.