Yeah, that endpoint is a little odd. We wanted to warn staff members about the number of potentially affected users and offer them the ability to choose between applying the change retroactively or not.
That’s why you’re seeing the “{ 'user_count': 2, ... }” in the response from the server.
I’ve clarified the error message so it makes more sense and also improved the front-end code to better handle this “use case” as well as adding specs