Description of problem:

 A non-admin user, even when granted the full System Admin role, experiences a significant delay (1-2 minutes) before a newly created organization becomes visible in both the Web UI and via the API. The built-in admin user does not have this delay.

How reproducible:

1. Log in to the Satellite Web UI as the admin user.

2. Navigate to Administer > Users > Create User and create a new user (e.g., test-user).

3. Navigate to the newly created test-user's details page, go to the Roles tab, and assign the System Admin role.

[root@sat617 ~]# hammer role info --id 4
Id:          4
Name:        System admin
Builtin:     no
Description: Role granting permissions for managing organizations, locations, users, usergroups, auth sources, roles, filters and settings. This is a very powerful role that can potentially gain access to all resources.

4. Log out and log in with the new test-user in a separate browser session.

5. Navigate to Administer > Organizations > New Organization and create a new organization (e.g., test-10).

Is this issue a regression from an earlier version:

Actual behavior:
[Describe the issue in detail, including what is happening and where]

UI Behavior: Immediately after creation, the UI redirects to a page showing the error:

Organization not found
Please try to update your request

If the user navigates back to the organization list, a warning banner may appear:

Warning alert:Warning
Organization you had selected as your context has been deleted

The new organization only appears in the list after a delay of 1-2 minutes.

API Behavior: The delay is confirmed at the API level. A polling script that queries the 1/katello/api/organizations1 endpoint shows a variable delay before the new organization's label is found in the results.

Example Timings:

# Test for "test-10"
✅ Success! Label 'test-10' found.
Total time taken: 53 seconds.

# Test for "test-7"
✅ Success! Label 'test-7' found.
Total time taken: 110 seconds.

# Test for "test-9"
✅ Success! Label 'test-9' found.
Total time taken: 52 seconds.

In contrast, a similar API check performed by the admin user shows the organization immediately.

Expected behavior:
[Describe what should be happening instead]

The newly created organization should be immediately visible to the user who created it (test-user), both in the UI and via the API, without any delay. The behavior should be consistent with that of the built-in admin user.

Business Impact / Additional info:

This bug significantly degrades the user experience and core administrative functions, leading to major operational and security issues.

Blocks Critical Automation: It stops essential automation scripts (Ansible, Terraform, etc.) from working. Any script that tries to configure an organization immediately after creating it will fail because the organization cannot be found.

Disrupts User Workflow: It interrupts administrators' work, forcing them to stop and wait for an unpredictable amount of time (1-2 minutes) before they can continue with their next task.

Undermines Security Policy: It forces users to rely on the shared, built-in admin account to avoid the delay. This bypasses security best practices for role-based auditing (knowing who did what).

Confuses Users: It provides misleading error messages (e.g., "Organization not found") for an operation that was actually successful, which reduces trust in the system.