--- title: "Common problems" description: "Fixes for the most common issues with sign-in, sync, and repo detection." url: "https://teamcadence.ai/docs/troubleshooting/" --- ## "Your session has expired. Sign in to resume." GitHub OAuth sessions expire periodically. Click through the sign-in prompt from the tray - it reuses your existing org/repo selection, so you won't have to redo onboarding. ## "Uploads are failing. Check your connection." Cadence retries automatically, but persistent failures are usually one of: - No network connectivity, or a proxy/VPN blocking outbound requests - A firewall blocking Cadence's background process specifically Check the tray's attention banner for more detail, and confirm the app isn't paused (see below). ## A repo isn't showing up Repo discovery works by finding local folders where a supported agent has actually run a session, then matching those against your org's GitHub repos. If a repo is missing: - Make sure you've run at least one session with a supported agent in that folder - Cadence can't discover a repo it's never seen activity in. - On macOS, check that Cadence has folder-access permission if the repo lives under Documents, Desktop, or Downloads (System Settings → Privacy & Security). - Use **Locate** from the tray's repo status view to point Cadence at the folder directly instead of waiting on auto-discovery. - Confirm the repo actually belongs to the org you selected during onboarding - Cadence only tracks one org per install (see [Orgs & repos](/docs/concepts/orgs-and-repos/)). ## Sessions aren't uploading even though the repo looks fine Check that: - The daemon isn't paused (tray icon shows "Paused" instead of "Idle"/"Syncing") - The repo is enabled - a repo showing up in discovery isn't automatically tracked - You're signed in and the org selection matches the repo's actual org ## The CLI can't find my sign-in The `cadence` CLI shares sign-in with the desktop app via `~/.cadence/cli/config.toml`. If `cadence auth status` shows signed out, sign in through the desktop app first - the CLI doesn't have its own separate login flow. ## Still stuck? Reach out at [[email protected]](mailto:[email protected]) with your OS, Cadence version (visible in the tray's overflow menu → changelog), and what you were trying to do.
Docs/Common problems
Common problems
Fixes for the most common issues with sign-in, sync, and repo detection.
“Your session has expired. Sign in to resume.”
GitHub OAuth sessions expire periodically. Click through the sign-in prompt from the tray - it reuses your existing org/repo selection, so you won’t have to redo onboarding.
“Uploads are failing. Check your connection.”
Cadence retries automatically, but persistent failures are usually one of:
- No network connectivity, or a proxy/VPN blocking outbound requests
- A firewall blocking Cadence’s background process specifically
Check the tray’s attention banner for more detail, and confirm the app isn’t paused (see below).
A repo isn’t showing up
Repo discovery works by finding local folders where a supported agent has actually run a session, then matching those against your org’s GitHub repos. If a repo is missing:
- Make sure you’ve run at least one session with a supported agent in that folder - Cadence can’t discover a repo it’s never seen activity in.
- On macOS, check that Cadence has folder-access permission if the repo lives under Documents, Desktop, or Downloads (System Settings → Privacy & Security).
- Use Locate from the tray’s repo status view to point Cadence at the folder directly instead of waiting on auto-discovery.
- Confirm the repo actually belongs to the org you selected during onboarding - Cadence only tracks one org per install (see Orgs & repos).
Sessions aren’t uploading even though the repo looks fine
Check that:
- The daemon isn’t paused (tray icon shows “Paused” instead of “Idle”/“Syncing”)
- The repo is enabled - a repo showing up in discovery isn’t automatically tracked
- You’re signed in and the org selection matches the repo’s actual org
The CLI can’t find my sign-in
The cadence CLI shares sign-in with the desktop app via ~/.cadence/cli/config.toml. If cadence auth status shows signed out, sign in through the desktop app first - the CLI doesn’t have its own separate login flow.
Still stuck?
Reach out at [email protected] with your OS, Cadence version (visible in the tray’s overflow menu → changelog), and what you were trying to do.