A connected surface is not showing data
Check GitHub source data, freshness and installation access.
- What you're seeing
- A GitHub-backed pull request cannot load, shows an earlier state or cannot perform an action.
- What it means
- The connection, repository access or current pull-request head needs checking. A briefly cached response may lag a change in GitHub.
- What to do
- Reload the pull request and check it directly in GitHub. If access still fails, ask an administrator to check both GitHub App cards in Integrations and the selected repositories.
- If you do nothing
- An old response can remain visible for days without proving the current GitHub state. A refused read cannot become current while the connection remains unavailable.
Check the source
Open the same repository and pull request in GitHub. Confirm that it exists and that your account can see it. Your personal access and the App installation’s access are separate checks.
Check freshness
The application caches review responses briefly: pull-request lists for 15 seconds and changed files for 60 seconds. Reload after the source changes. If the pull-request head moved, inspect the current diff before retrying an action. An expired cache entry requires a new provider read; it is not an offline copy to keep working against.
Check access
Ask an administrator to check the GitHub account and repository selection on both GitHub App cards. Read any failure’s Details and keep its reason and trace identifier. See a connection failed or lacks a scope for confirmation and permission checks.
For a tool without a supported setup control, there is no connected surface to repair through Integrations. An external link or embedded preview doesn’t establish a provider connection.