A connection failed or lacks a scope
Diagnose GitHub installation, repository access and permission refusals.
- What you're seeing
- GitHub setup is waiting for confirmation, reports a failure, or cannot reach the expected repository.
- What it means
- The installation may still need GitHub approval, the selected account or repositories may not match, or a permission or repository rule may refuse the action.
- What to do
- Ask an administrator to open Integrations in the organisation settings. Check both GitHub Apps separately, including the account on each card. Read Details for the reason and trace identifier before retrying.
- If you do nothing
- A pending owner approval can wait for days and still needs that owner's action. A refused repository action remains refused until an administrator resolves its stated cause.
Check the installation state
Connected means the application’s installation check succeeded for that App. Both Apps need the intended account; a working installation for one does not complete a missing installation for the other. If confirmation times out, use Check again. For a failed attempt, correct its stated cause and use Try again. A pending organisation request needs approval in GitHub.
Check the repository and action
Check the account and repository selection shown on the cards. A successful installation doesn’t grant access to repositories outside that selection. GitHub’s branch protection and merge rules also apply. Don’t assume every failure needs a wider permission grant.
If a member cannot inspect installation settings, send an administrator the repository, intended action and exact refusal text. Include the trace identifier when one appears. Don’t send access tokens.
Reconnect only when needed
There is no generic Reconnect control. After a completed disconnect, install the affected App again through connect a provider. Disconnecting revokes working access and requests App uninstall, so it is not the first step for a confirmation delay.
Other tools have no supported consent or reconnect flow in Integrations. Keep using them directly rather than trying the GitHub procedure.