Skip to main content

Troubleshooting for Jira Reader

This topic lists common Jira Reader errors and symptoms with suggested resolutions.

Exception / symptom

Resolutions

HTTP 401 Unauthorized / 403 Forbidden

  • For OAuth: verify Client ID, Client secret, and Refresh Token. Ensure the app was created in Atlassian Developer Console and that offline_access was included when generating the authorization code.

  • Confirm the redirect_uri used in the token exchange exactly matches the app’s callback URL.

  • For API token: confirm Username (Atlassian account email), API Token, and Endpoint URL (for Atlassian Cloud, use https://<your-domain>.atlassian.net/).

HTTP 404 Not Found (endpoint or resource)

  • Check Endpoint URL (trailing slash and domain spelling). Use the Cloud URL for Jira Cloud.

  • Verify the table name(s) in Tables are supported (see “Jira Reader properties & supported tables”).

HTTP 429 Too Many Requests / Jira API rate limiting

  • Increase Polling interval and/or reduce Thread pool count.

  • Limit scope of Tables and avoid broad wildcards during initial testing.

“Invalid table names” (misconfigured objects)

  • Review Tables and Excluded tables for typos or mismatched names; remove unsupported objects.

  • If using wildcards, start with a narrow set, validate, then expand.

403 on Sprints / Roles / RoleActors tables (insufficient scopes)

  • For Sprints, add scope read:sprint:jira-software.

  • For RoleActors / Roles, add either manage:jira-configuration or the set: read:user:jira, read:group:jira, read:project-role:jira, read:project:jira, read:avatar:jira, read:project-category:jira.

  • For other tables, ensure read:jira-user and read:jira-work are present.

  • Re-generate tokens after changing scopes.

Duplicate records appearing after restarts

  • This can occur with A1P recovery or when objects lack a reliable incremental marker.

  • Configure target writers in upsert/merge mode where possible to de-duplicate.

  • Exclude objects that do not support incremental load, or accept periodic full refresh for those tables.

Missed or out-of-order changes

  • Review Incremental load marker. Prefer a monotonically increasing field (for example, a timestamp). Using a non-increasing ID can cause gaps.

  • Adjust Start position to re-read from a known safe watermark if needed.

Authentication flow fails (authorization code / token exchange)

  • Ensure the authorization URL included offline_access and required Jira scopes.

  • Confirm client_id, client_secret, code, and redirect_uri values in the token request are correct and URL-encoded where necessary.

  • Check system time skew on the Striim host; excessive skew can break OAuth exchanges.

Slow reads or high CPU during broad polls

  • Narrow Tables to only required objects; avoid fetching large audit-heavy objects if not needed.

  • Tune Thread pool count and Connection pool size to match available resources.

“Unauthorized” for connected accounts

  • When reading a connected account, set properties for the correct account context (for example, use the right site/tenant and verify that the credentials have access to that account’s data).

General connectivity failures

  • Verify outbound access from the Striim host to Atlassian endpoints (proxy, firewall, TLS interception).

  • Confirm TLS 1.2+ is enabled; update JVM truststore if your environment uses custom CAs.