Contents

Help

Troubleshooting

A fix pull request is waiting for review instead of merging

Akesis's comment on the pull request says why, under Why. The usual reasons:

  • CI hasn't finished, or failed. Akesis decides again when CI completes.
  • diff-size: the change is larger than the repository's maximum outside lockfiles. Raise the limit on the repository's autonomy page if that's expected.
  • coverage-floor: no coverage report for that commit, or one below the floor. Check that your CI sends coverage in the same job as the tests, for the pull request's head commit; see Scanners and uploads.
  • Compatibility: the fix brings in a package whose peer dependencies aren't met, breaks another package's peer requirement, or needs a newer Node.js than your project declares. The comment names the package; fix it by hand, or update the conflicting package first.
  • Provenance: the lockfile doesn't match the registry's published hashes, a Python lockfile pins no hashes, a signature or build record doesn't verify, a release dropped the build record its predecessor had or was built from a different repository, or the ecosystem isn't npm, Python, Go or Rust. These always stop at review.
  • Allowed files or sensitive paths: the change touches files outside manifests and lockfiles, or a path you marked sensitive.
  • The repository isn't at T3, or its test suite isn't verified.

A Dependabot pull request isn't linked to a finding

Akesis links a pull request only to active findings for the same package, when the pull request upgrades to or past the fixed version. Check that the finding exists in the backlog for that repository. If the repository was just added to the GitHub App, Akesis syncs its alerts and links waiting pull requests within a couple of minutes. On Bitbucket and GitLab, the account that opened the pull request must be one you chose under Find fix PR accounts.

A repository I added on GitHub doesn't appear

Repository access is set on GitHub, on the app installation's Configure page; see Code hosts. Akesis picks up the change within about 5 minutes. Add another GitHub account in Akesis is only for a different organization or user.

The backlog says exploit data is stale, or a scanner is failing

Exploit data (EPSS and CISA KEV) refreshes daily. A warning means a refresh failed or the data is more than three days old; Akesis keeps using the last good data and says how old it is. A failing scanner shows its last error above the backlog; the usual cause is an expired or replaced token, which an admin can update under Integrations.

Narratives say AI is unavailable

AI narratives are optional and may not be enabled for your organisation. Settings → AI features shows the status. Nothing else depends on AI.

A page says "Failed to fetch"

The browser couldn't reach Akesis at all, which is usually a network or VPN problem rather than anything you entered. Reload, and try without the VPN if it persists.

Everything needs to stop now

Stop all autonomy, in the header. It takes effect before the next merge, including merges already approved.