Tracker connection failed
Symptom
Section titled “Symptom”An error alert appears on the Dashboard indicating the tracker connection failed. The board may show stale data or no issues at all.
Causes and fixes
Section titled “Causes and fixes”Expired or revoked credentials
Section titled “Expired or revoked credentials”Your GitHub personal access token or Jira API token may have expired or been revoked.
Fix: Generate a new token and update it in Settings -> Issue Tracker. See Credentials for instructions for each tracker.
Missing token scopes (GitHub)
Section titled “Missing token scopes (GitHub)”Your GitHub PAT may not have the scopes Cate needs.
Fix: Check your token’s scopes in GitHub -> Settings -> Developer Settings -> Personal access tokens. The required scopes are repo, project, and read:org (for organization repositories). Regenerate with the required scopes and update the token in Cate.
Invalid Jira credentials
Section titled “Invalid Jira credentials”The Jira site URL, email, or API token may be incorrect.
Fix: Verify the site URL (no https:// prefix, no trailing slash — just mycompany.atlassian.net), confirm the email matches the account that owns the API token, and regenerate the token if needed.
Project board deleted or reconfigured
Section titled “Project board deleted or reconfigured”The project number or board ID in .cate/workflows.json may not match your current board.
Fix: Check tracker.projectNumber (GitHub) or tracker.jira.boardId (Jira) in .cate/workflows.json against your actual board. Update the file if they don’t match, or re-run setup.
Network connectivity
Section titled “Network connectivity”A transient network issue prevented Cate from reaching the tracker API.
Fix: Check your internet connection. Cate retries automatically on the next poll cycle. If the error persists, check your tracker’s status page.