Skip to content

Boot failure screen has no retry after a successful sign-in #694

Description

@sanskar0627

What happened?

If /me succeeds but the follow-up boot calls fail (GET /api/v1/models and GET /api/v1/capabilities), the UI is a dead end:

Failed to load application configuration: Failed to fetch

Expected

A proper error screen with a way to retry, matching the existing sign-in failure screen (AuthErrorScreen) that has a card, explanation, and Try again button.

Actual

A blank white page with a single red line of text. There is no heading, no card, and no Retry button.

A full page refresh is the only recovery, and it still fails while those requests are down.

Code: packages/frontend/src/App.tsx (boot.status === 'error')

Contrast: packages/frontend/src/AuthErrorScreen.tsx

1.Broken: white page, red Failed to load application configuration: Failed to fetch. Request conditions shows both URLs blocked, 1 affected each.

Image

2.Healthy: same app with blocking off; Settings → Models loads normally.

/api/v1/auth/me still succeeds. Only models + capabilities are blocked.

Image

Suggested fix

UI-only in packages/frontend:

  • Reuse the auth-screen card (logo, title, message).

  • Add a Retry button that re-runs the existing boot request instead of requiring a full reload.

  • Keep the current error text as the supporting message.

I would like to implement this after a maintainer approves.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions