Troubleshooting

The app says authentication is required

Reload the Jira page and open License Radar as a Jira site administrator. If the message continues, check that the app is installed on the current site and that the Atlassian session is still valid.

The app says it cannot read users or activity

Check the installation permissions and ask an administrator to retry. A 403 means the requested Jira data is not available to the app; it is not evidence that users have no activity.

Jira is rate limiting the scan

A 429 means Jira asked the app to slow down. Wait and retry later. Do not start several scans at once; License Radar uses a scan lock to prevent duplicate work.

Jira returned a server error or timed out

500-class responses and timeouts can be temporary Jira or Forge conditions. Retry after a short wait and check the scan state. If a scan becomes PARTIAL or FAILED, use only the completed evidence and do not read the result as zero candidates.

The scan is empty

An empty completed scan means no supported Jira access or no candidate met the configured signal in the data returned. It is different from a failed scan. Check the analysed-user count, coverage and status before drawing a conclusion.

Activity is missing for a person

The activity signal is built from visible Jira issue updates associated with assignees, reporters and creators. A missing date is insufficient evidence. It does not mean the person never logged in or never used Jira.

The estimate looks different from the invoice

License Radar does not read your Atlassian contract, discounts, taxes or final invoice. Check the currency, product or total-spend assumption and threshold. The result is an estimated cost associated with access worth reviewing, not a billing statement.

Contact support

Use Create a support request and include the Jira site URL, app version, scan status, approximate time, steps to reproduce and a sanitised screenshot if useful. Never send passwords, API keys, personal access tokens, OAuth secrets or full exports.