Skip to main content

Troubleshooting

Find your symptom below. Many problems show up on the System health page first, so look there: it shows whether Gryndel can reach GitLab, its GitHub App and the models. For problems with the Gryndel server itself, contact your Gryndel operator (usually your IT or platform team).

Signing in​

"Sign in with GitLab" or "Sign in with GitHub" shows an error​

Try again in a private browser window. If it still fails, the problem is on the server: tell your operator the exact message.

There is no "Sign in with GitHub" (or GitLab) button​

Gryndel only offers the hosts your operator has set up for sign-in. Ask them to turn on the one your team uses.

GitLab or GitHub says the redirect URI isn't valid​

GitLab says "The redirect URI included is not valid"; GitHub says "The redirect_uri is not associated with this application". Use the exact Gryndel address your team gave you. A different host name (for example, an old address) won't work. If the address is right, the operator's GitLab application or GitHub App doesn't know Gryndel's address. Tell your operator.

I signed in but see no workspace​

No workspace exists for your group or account yet, you aren't a member of it, or you signed in with the other host. See Sign in: I see no workspace.

I see my GitLab workspaces but not my GitHub ones (or the reverse)​

A session belongs to the host you signed in with. Sign out and sign in with the other. See One host at a time.

I'm a viewer but should be an admin​

Roles come from GitLab or GitHub. GitLab group Owners and Maintainers, and GitHub organisation owners, are admins by default. Check your access there, or ask a workspace admin to change your role on Members.

On GitHub, if every organisation owner is a viewer, Gryndel's App is missing the Members permission. See Prepare your GitHub account.

I was signed out​

Your session ends when your GitLab or GitHub sign-in token expires; on GitHub, after about eight hours. Sign in again.

Setting up​

My group or account isn't listed in "New workspace"​

  • You must be an Owner or Maintainer of the group, and signed in with GitLab.
  • A workspace may already cover a parent group or a subgroup. Workspaces can't overlap.
  • Tick Include subgroups, or paste the full group path.

"Add @… to … as a Developer first"​

GitLab only. Add the reviewer account to the group as a Developer first. See Prepare your GitLab group.

"GitLab refused the token" or "expires in … days"​

GitLab only. The workspace's reviewer token was revoked or has expired, or soon will. Reviews in the workspace stop while GitLab refuses it. A workspace admin makes a new token for the same account and pastes it under Reviewer account on the Workspace page.

A repository is missing from Repositories​

Click Refresh projects (GitLab) or Refresh repositories (GitHub). Otherwise Gryndel reads the list again once it is 15 minutes old.

  • GitLab: Gryndel's GitLab account must be able to see the project, so it must be in the workspace's group or a subgroup. A project in a deeper group with its own workspace is listed there instead.
  • GitHub: the repository must be in the App's installation. Add it on GitHub; see Change the repositories later. If Repositories says "GitHub discovery is unavailable", check that the App is still installed on the account.

Turning on a repository fails​

On GitLab, turning on a repository adds its webhook as you:

  • You need Maintainer access to that project in GitLab.
  • If GitLab says The requested scope is invalid, Gryndel's GitLab application is missing the api scope. Tell your operator.
  • If you denied the permission request, repeat the action and allow it.

On GitHub, there is no webhook to add. If it fails with "Repository is not accessible in this workspace's GitHub account", the repository has left the App's installation: add it back on GitHub, then click Refresh repositories.

Reviews​

A review never starts​

  1. Is the repository turned on and not paused? Check Repositories.
  2. Is the merge or pull request paused? Comment @gryndel resume, then @gryndel review to review the latest commit now (resume alone waits for the next push).
  3. Are reviews on for the workspace? Check Workspace.
  4. Did the webhook arrive, and can Gryndel reach the repository?
  • In GitLab, open the project's Settings → Webhooks, then Edit on Gryndel's hook, and look at Recent events. Failed deliveries usually mean the GitLab server can't reach Gryndel. Send your operator the error.
  • Gryndel's GitLab account must be a Developer of the group.

Gryndel also checks the open merge and pull requests of turned-on repositories on its own, and reviews those whose latest commit it hasn't reviewed, so a missed delivery is usually caught later.

To ask for a review by hand, comment @gryndel review on the merge or pull request. It doesn't get past a paused or disabled repository, or reviews turned off for the workspace; check those first. See Investigate a review that went wrong.

Gryndel ignores my @gryndel command​

  • You don't have the access. Commands need the Developer role or higher on GitLab, or write access to the repository on GitHub. Gryndel replies saying so.
  • The word is different. On GitHub, @gryndel is a word Gryndel watches for, not a real mention, and your operator can change it. Check with your team.
  • The comment was edited. On GitHub, Gryndel reads new comments only. Post the command again in a new comment.
  • The webhook didn't arrive. See A review never starts.

"fixes: apply" posts a notice on GitHub instead of a commit​

Gryndel can't apply its suggestions on GitHub. Use GitHub's Commit suggestion on the findings you agree with. On GitLab, the same kind of notice means Gryndel couldn't push to the branch, for example because it is protected.

A review failed​

Open it on Pull requests to see the error. Fix the cause, then replay it or comment @gryndel review. The most common causes are model problems; see below.

"GitLab's API rate limit … was reached"​

GitLab limits how many requests each account makes; on gitlab.com's free plan it is 100 a minute. Gryndel waits and tries again by itself, so a busy minute only delays a review. If the review still failed, replay it once the minute has passed. Many large merge requests at once can reach the limit again; GitLab's paid plans allow more.

A review is slow or stuck​

Comment @gryndel status to see which step it's on. Gryndel sends a review again by itself when it hasn't progressed for 15 minutes. Comment @gryndel cancel to stop it.

Models​

A banner says the model is no longer available or the key was rejected​

The provider withdrew the model, or no longer accepts the API key. Pick another model or enter a new key in Model settings, then click Test connection.

The review fails with context_unknown​

The provider doesn't report how much text the model can read at once. Set Context window on the provider in Model settings.

The review fails with structured_output_unsupported or model_restricted​

The model can't return the structured answers Gryndel needs, or the provider only serves it to certain apps. Choose another model.

The model server can't be reached​

The Gryndel server must be able to reach the model, not your computer. Check the address in Model settings, and ask your operator whether the server can reach it.

Contacting your operator​

When you report a problem, include:

  • the workspace, repository and merge or pull request;
  • the time it happened;
  • the exact error message from the review or the System health page.

Don't paste API keys, tokens or private code into the report.