Why Selecting Phased release releases the app to all users?

Browser used: Microsoft Edge
Portal: Itunes Connect - https://itunesconnect.apple.com/

Description of the issue
I regularly use phased release for my application. I usually use chrome browser to manage itunesconnect.

on 17th August 2020, the on choosing phased release, the phased release widget appeared once and with a flicker it went away and never to be visible again.

Only later I realized that the app has been rolled out to 100% users.

Questions:
  1. Why did this happen?

  2. Since this was irreversible decision, it costs us a lot to managed any damage this action costs, please prepare a feature to reverse (at least partially) to the phased rollout.

  1. ) Why not use a native browser...Safari. All bets off with non-native tools.

  2. ) As forums posts are not feature requests, feel free to file one via the bug/feedback reporter, linked below, being sure to add your report number to your thread for reference, thanks and good luck.

We also had the same issue today (30-9-2020). My colleague and I planned to start a phased release for our app. We double checked everything with multiple people. Everything was correct. And of course we double double checked if we are making use of the phased release option. We can tell you that this option was selected. After going live we noticed that the app was fully released. We are 1000% sure did everything right. We have used safari and Chrome, and on both browsers it occurred. This is the third time we face this issue. We normally do a phased release. Is there a way to prevent this? Is Apple even familiar/aware of this bug?
We also had the same issue yesterday (30-9-2020). My colleague and I planned to start a phased release for our app. We double checked everything with multiple people. Everything was correct. And of course we double double checked if we are making use of the phased release option. We can tell you that this option was selected. After going live we noticed that the app was fully released. We are 1000% sure did everything right. We have used safari and Chrome in the past and on both browsers it occurred. This is the third time we face this issue. We normally do a phased release. Is there a way to prevent this? Is Apple even familiar/aware of this bug?
RE:
1) Why not use a native browser...Safari. All bets off with non-native tools.
2) As forums posts are not feature requests, feel free to file one via the bug/feedback reporter, linked below, being sure to add your report number to your thread for reference, thanks and good luck.

So if KMT is using a windows laptop, they should only use Internet Explorer when using app connect? Silly response. Its an app connect bug.


Why Selecting Phased release releases the app to all users?
 
 
Q