Troubleshooting

Connected Apps

Symptom	Likely cause	Action
Callback or authorization fails	Incorrect callback URL or app created in the wrong environment	Check the callback URL shown in your Acrity installation and update the app in the provider
Installation appears invalid	Permission removed or token revoked	Use Reauthorize in Connected Apps
Repository does not appear	App was not installed on that repository or organization	Adjust the installation in the provider, then sync again
PM comments are not posted	The PM integration is not linked to the repository, or lost permission	Review the link on the repository detail page

Credentials

Managing credentials requires a Workspace admin.

Symptom	Likely cause	Action
Credential invalid	Token expired, revoked, or has insufficient permission	Edit or rotate the credential, then use Validate
Repository has no readiness	A VCS or PM credential is missing	Open the repository detail page and link the credentials
Provider returns permission denied	Insufficient scope in the provider	Update permissions in the provider and validate again

Connectors

Managing connectors requires a Workspace admin.

Symptom	Likely cause	Action
Connector offline	Service stopped, network blocked, or token rotated	Check the local service, proxy, and installed secrets, then Revalidate
Private repositories do not appear	Local token lacks permission or the instance URL is incorrect	Review the local configuration and Revalidate
TLS or certificate error	Corporate proxy or untrusted CA	Configure the certificate chain required by your company
Revalidation fails after rotation	The new secret was not applied on the host	Update the local vault or environment, restart the connector, then Revalidate

Outbound webhooks

Managing webhooks requires a Workspace admin.

Symptom	Likely cause	Action
`401` or `403` at destination	Invalid destination token or header	Update the secret headers in the webhook
Invalid signature	Different HMAC secret in Acrity and the receiver	Rotate the secret and test again
Timeout	Destination is slow or unavailable	Test the URL outside Acrity and review the receiver timeout
Payload rejected	Template incompatible with the destination	Use preview and test before activating

API keys

Managing API keys requires a Workspace admin.

Symptom	Likely cause	Action
`401`	Key missing, invalid, expired, or inactive	Confirm the `X-Acrity-Key` header, validity, and key status
`403`	Insufficient scope	Add the required scope or create a new key
`429`	Usage limit reached	Apply backoff and reduce concurrency
Integration stopped after rotation	The old secret is still in use	Update the vault and restart the automation

Billing

Symptom	Likely cause	Action
Reviews blocked by billing	Trial ended, wallet balance insufficient, or spend cap reached	Open Billing to top up the wallet or adjust the spend cap. Plan changes are handled by Acrity — contact support
Payment portal does not open	Your role cannot manage billing	Ask a Workspace admin or Billing Manager to complete the payment
Top-up does not appear	Payment is pending or failed	Check the wallet history and payment method

Repositories

Managing repositories requires a Workspace admin.

Symptom	Likely cause	Action
Review does not start	Webhook not configured, repository paused, or a branch rule ignores the change	Review the repository detail page, then confirm on the operations dashboard whether the review was queued
Comment does not appear in the PR or MR	Result posting disabled or insufficient permission	Validate the credential and the statuses/checks in the provider
Result appears in an unexpected language	Language override on the repository or workspace	Review the language setting on the workspace and repository detail page
Bootstrap unavailable	Repository is not eligible or setup is incomplete	Open the Bootstrap tab and follow the displayed guidance

Triage flow