Common problems with Codacy

When you add the integration

What you see	What to do
Account API token is required.	Paste the account API token in Account API token.
app.codacy.com refused the credentials (401). Check the token, and that it has not expired. Fix the field above, or save anyway if the source is only unreachable for now.	The token is wrong or expired. Create a new account API token in Codacy and paste it in Account API token.

After you add it

What you see	What to do
On the Codacy card of Administration › Plugins, a greyed switch and Configure the Codacy integration first	Add the integration: Add the Codacy integration.
In Administration › Problems, a Company connection line Codacy: app.codacy.com refuses the credentials (401). The token may be wrong or expired.	Click Fix it: it opens the integration. Paste a new token.
No Codacy card on the component overview, no Codacy tab	Add the codacy.com/project-slug annotation to the component, and turn on Enable Codacy in Administration › Plugins.

When the tab says a module is missing

What you see	What to do
Astrolabe does not offer this Codacy feature on this instance. and A module is missing from this Astrolabe installation. Tell your Astrolabe administrator.	The integration may be connected and the plugin on, but this installation of Astrolabe lacks the module that serves Codacy. Tell your Astrolabe administrator. Nothing to change on the component.

Not verified on an instance yet: this message needs an installation that lacks the module.

Still stuck?

Write to support@forgeit.fr with the name of the component and the message you see.