Troubleshooting Sync Issues
Fix common CLI sync problems quickly.
Updated 2026-07-27
Use this page to diagnose and fix common sync failures.
No linked repos found
Run:
workrail link
Then retry:
workrail sync
Authentication expired
Re-authenticate:
workrail auth login
No new entries after sync
- Confirm the repository has commits in the selected range.
- Check the Impact Snapshot page. Accepted activity can still be processing; the page refreshes automatically.
- For an intentional recent Pro backfill, run:
workrail sync --since 7d
Do not rerun sync repeatedly while the page says evidence is processing.
Sparse or old Git history
Free setup considers up to six months of selected repository history. If there is no useful activity in that period, open Entries and add one real accomplishment manually. Manual evidence is eligible for the snapshot.
Repo linked to wrong project
Reset mapping:
workrail unlink
workrail link
Autosync looks stale
Check service state:
workrail autosync status --verbose
If needed, restart autosync:
workrail autosync disable
workrail autosync enable
Snapshot generation failed
Open Impact Snapshot and retry. A generation failure does not modify or delete the original entries. If the snapshot says there is insufficient evidence, add one entry or sync a repository with activity in the snapshot period.
Still stuck?
Email: [email protected]
Next steps
Was this page helpful?