GitHub Copilot Troubleshooting
Use this guide to resolve issues related to GitHub Copilot metrics, authorization failures, scope mismatches, and unexpected adoption behavior. 403 AiMetricsUnauthorizedException. Symptom Connection…
Use this guide to resolve issues related to GitHub Copilot metrics, authorization failures, scope mismatches, and unexpected adoption behavior.
403 AiMetricsUnauthorizedException
Symptom
- Connection fails during setup
- No Copilot data appears in AI Insights
- 403 Unauthorized error
Root cause
- GitHub Copilot Usage Metrics policy is not enabled at the organization level.
Resolution
- Enable Copilot usage metrics in GitHub organization settings.
- Reauthorize the integration in LinearB.
No data after successful connection
Possible causes
- Initial backfill still processing (up to 90 days).
- Copilot is enabled but not actively used.
- Token lacks required scopes.
Resolution
- Wait for initial sync to complete.
- Verify PAT includes required scopes (
user:read,read:org). - Confirm Copilot usage metrics policy is enabled.
Adoption Rate above 100%
Symptom
- Adoption rate exceeds 100% in AI Insights.
Explanation
Copilot usage is measured at the GitHub organization level, while Git activity in LinearB may be scoped to a subset of repositories. If Copilot users exist outside the connected repository scope, the denominator (Git active users) may be smaller than Copilot active users.
Resolution
- Expand repository coverage in LinearB.
- Align GitHub organization selection with repository scope.
Missing organizations
Symptom
- Expected GitHub organizations do not appear during configuration.
Root cause
- The Personal Access Token does not have visibility into those organizations.
Resolution
- Regenerate the PAT with correct organization access.
- Confirm token owner has access to the target organizations.
User-level data missing
Organization-level Copilot data may appear even if individual users are not visible in the Users page.
Possible causes
- Copilot usage metrics policy not fully enabled.
- GitHub users not mapped to LinearB users.
- Token scope limitations.
Resolution
- Verify policy settings.
- Verify GitHub user mapping.
- Reauthorize if needed.
Reauthorization required
If the integration shows Disconnected:
- Generate a new PAT.
- Reauthorize in Settings → Company Settings → AI Tools → GitHub Copilot.
Still experiencing issues?
If the issue persists, contact LinearB Support .
How did we do?
Enabling LinearB AI Services
Troubleshooting Missing AI Metrics