Insights fail to load or are stale

FleetHQ shows We couldn't load your insights, or it leaves existing rows on screen with Showing the insights we loaded last, the most recent refresh failed.

Neither message is an all-clear. FleetHQ cannot confirm the current finding list until a refresh succeeds.

Diagnostic steps

  1. Read the state shown in the workspace.

    • A loading skeleton means the first request has not completed.

    • We couldn't load your insights means no usable list is available.

    • Showing the insights we loaded last means the visible rows came from an earlier successful response.

  2. Confirm the working tenant. If you recently switched tenants, verify that the selector shows the intended tenant.

  3. Select Try again. Wait for the button to finish before selecting it again.

  4. Check the freshness label. After a successful load, Last analyzed identifies the latest successful FleetHQ processing run. It is not the browser refresh time.

  5. Reload the page once. This re-establishes the current tenant context and requests a fresh list.

  6. Check access if the error persists. Confirm that FleetHQ is on for the tenant and that your role still has View FleetHQ.

  7. Compare with another authorized user. If the same tenant fails for both users, contact RTA Support.

Resolution paths

The retry succeeds

The explicit error or stale notice clears. Review the current list and Last analyzed time before acting.

Old rows remain with a stale notice

You may read the earlier rows for context, but do not treat them as the current fleet state or record a decision that depends on freshness. Try again later or reload. If the notice persists, contact RTA Support.

The error detail names access or configuration

Follow FleetHQ is not available. A tenant switch or permission issue must be corrected before retrying the list.

Escalate to RTA Support

Include the tenant, approximate time, exact visible error detail, whether Try again failed, and the displayed Last analyzed time if older rows remain. Do not report the empty baseline message as an error; it represents a successful empty response.

See also

Search