Permission errors

Permission errors usually mean the Zapat GitHub App has lost access to a repository, or the GitHub App token has expired. Here is how to diagnose and fix each type.

"Repository not registered with Zapat"

This means the repository is not in Zapat's system. This happens when:

• You added the repo to the GitHub App installation but did not connect it in the Zapat dashboard.
• The repo was connected but then disconnected.
• You are working in a repo that belongs to a different GitHub account than the one you linked.

Fix: go to Repositories in the Zapat dashboard and connect the repository. If the repo does not appear in the list, update the GitHub App installation to include it.

"GIT_CLONE_FAILED" — Cannot access the repository

The agent could not clone the repository. This usually means:

• The GitHub App installation was updated and the repo was removed from the selected repos list.
• The repository was made private after the GitHub App was installed, and the App no longer has the necessary permissions.
• The GitHub App installation token expired and could not be refreshed (rare).

Fix: go to GitHub > Settings > Installed GitHub Apps > Zapat > Configure, and verify the repository is in the "Repository access" list. If not, add it.

"UNAUTHORIZED" on webhook delivery

Zapat rejected the webhook because the HMAC signature did not match. This should not happen under normal conditions. It can occur if:

• The GitHub App webhook secret was rotated without updating Zapat's configuration.
• The payload was modified in transit (very rare).

Fix: contact support@zapat.ai — this requires Zapat to rotate the webhook secret on our side.

API key permission errors

If you are using the Zapat API and receive a 403 Forbidden response, the API key does not have the required permission for the operation. Check the permission required for the endpoint in the API documentation and create a new key with the appropriate permission.