Skip to content

Improve error handling for rate limits and timeouts #163

Open
Open
Improve error handling for rate limits and timeouts#163
Labels
area: ai-logicRelated to Gemini prompts, tokens, or model responses.area: backendRelated to Next.js API routes or Octokit/GitHub API.area: frontendChanges specifically for the UI/Tailwind components.bugSomething isn't workingci/cdAutomated workflows for building, testing, and deploying code.typescriptType definition fixes, interfaces, or TS configuration.
@naheel0

Description

@naheel0
naheel0
opened on May 27, 2026

The API should distinguish upstream GitHub, model, timeout, and permission failures so users get actionable feedback instead of a generic failure state.

Proposed scope

  • Detect rate-limit responses from GitHub and the model provider.
  • Add a timeout-specific error message.
  • Keep the current auth-required flow intact.

Acceptance criteria

  • The UI shows a clear message when the upstream request is rate-limited.
  • Timeout failures have a separate user-facing explanation.
  • The existing auth-required path still opens the GitHub login flow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: ai-logicRelated to Gemini prompts, tokens, or model responses.area: backendRelated to Next.js API routes or Octokit/GitHub API.area: frontendChanges specifically for the UI/Tailwind components.bugSomething isn't workingci/cdAutomated workflows for building, testing, and deploying code.typescriptType definition fixes, interfaces, or TS configuration.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions