Team - “Oops” error when updating parent Team for a specific Team
When updating the parent Team for a specific Team, admins may receive a generic “Oops” error and the parent change does not save. This can occur due to a transient backend constraint issue on the Team hierarchy, and the same update may work later without configuration changes. Questions this answers: Why do I get an Oops error when updating a team's parent team? What should I do if I can't move a team under a new parent team?