Skip to main content

Troubleshooting

This page covers the most common issues when using AICockpit Adoption and how to resolve them. Most problems are related to authentication, provider configuration, repository scope, or missing synchronization data.

The Dashboard Shows No Data​

Symptom: The dashboard loads but displays empty states or no analysis results.

Possible causes and solutions:

  • No organization selected — Select an organization from the header dropdown. The dashboard only loads data for the active organization.
  • Provider not configured — Open Settings and complete the provider configuration before running synchronization.
  • No repositories selected — Verify that at least one repository is active in the Settings Repositories tab.
  • Synchronization not run — The dashboard requires a completed synchronization job for the selected period. Go to Synchronization and run a job first.

Authentication Keeps Loading​

Symptom: The application stays in a loading state after the login flow completes.

Possible causes and solutions:

  • Incorrect redirect URI — The SSO redirect URI configured for the environment may not match the application URL. Contact your administrator to verify the configuration.
  • Incomplete identity provider flow — The browser session may not have completed the provider authentication. Clear your browser cache and try again.
  • Session conflict — Log out from any existing sessions and attempt to log in again.

Provider Validation or Synchronization Fails​

Symptom: Saving provider settings or starting a synchronization job returns an error.

Possible causes and solutions:

  • Incorrect workspace or owner name — Double-check the workspace or organization name in the Settings Provider tab.
  • Invalid or expired token — Generate a new access token or app password and update it in Settings.
  • Insufficient repository permissions — Confirm that the token has read access to the selected repositories.

Repositories Do Not Appear​

Symptom: The repositories list in Settings is empty after saving the provider configuration.

Possible causes and solutions:

  • Invalid provider configuration — An incorrect workspace name or expired token prevents the application from retrieving the repository catalog. Verify and save the provider settings again.
  • No repositories in the workspace — Confirm that the configured workspace contains at least one repository accessible with the provided credentials.

Contributor Attribution Looks Incomplete​

Symptom: The dashboard shows repository activity but some contributors are missing or unrecognized.

Possible causes and solutions:

  • Missing user mapping — Upload a CSV mapping file in the Settings Mapping tab to reconcile version control identities with telemetry identities.
  • Mismatched identities — Confirm that the provider identity values in the CSV match the repository usernames exactly, and that the mapped emails correspond to the telemetry identities used by the application.

Still Need Help?​

If the issue is not listed here or persists after following the steps above, contact your platform administrator or open a support request through the appropriate channel for your organization.