Authorization failures should not look like loading

A settings panel can appear stuck when a query library retries fast HTTP 401 or 403 responses while the component renders only a generic loading state. Surface authorization failures immediately, and disable retries for non-retryable authorization responses where policy permits.

Confirm response status and latency before diagnosing database or pool starvation. Keep loading, authorization, and retryable transport failures as distinct UI states.