When the user possess all necessary permissions to create a Foreman location (eg: System Admin + Organization Admin roles), but Administrator checkbox is unset, location creation takes about 2 minutes.

It is as following. I navigate to Administer->Locations, then press "New location" button, enter the location name and click Submit button, and it stalls for 20 seconds.
Then the following error appears: "Location not found Please try to update your request". This message box contains only a single "Back" button. After I click "Back", it returns to the location list, but there is no new location in the list (yet). If I continue refreshing the page, after approximately 2 minutes the location appears in the list.

Same behavior can be observed when creating a location via REST API. Location creation request to /api/locations endpoint completes in as much as 20 seconds, but location is not immediately available after REST API query has completed. It becomes available only after 2 minutes.

If I set "Administrator" checkbox on the user, location creation is instant.
It looks like this "Administrator" checkbox contains some other permissions, not present in any other roles, like System Admin or Organization Admin. This should at least be better documented.

It is still unclear how to grant this kind of permission via LDAP group membership. Is it at all possible?

Besides, lack of permissions should not produce 2 minute slowdown, but rather some informational message.

We are running Foreman 3.12.1 with Katello on RHEL8.
Our environment contains 3000 hosts, 100 LDAP users, 275 locations. Each user is assigned a role via LDAP group membership to manage hosts only in their location.

No performance problems except this one.

Would be glad if you advise how to debug it.