Troubleshooting
- Exit
2means invalid arguments, configuration, or an incompatible cache/schema version. Correct the input; incompatible exports are regenerated, not migrated. - Exit
3means an operational failure such as corrupt cache data or an unwritable export target. A corrupt cache is regenerated bysync; preserve it first if forensic inspection matters. - Exit
4means partial synchronization. Prior valid repository data is retained and diagnostics identify what failed. - Exit
5means the token is absent, invalid, or unauthorized. Verify the configured environment variable and required repository access. - Exit
6means a primary, secondary, search, or configured request budget stopped the run. Wait for the reported reset/window before retrying; the plugin does not sleep through rate limits.
Use --log-level debug or trace for diagnostics. Logs remain on stderr and registered secret values
are scrubbed. Use sync --dry-run or export --dry-run to calculate the full change/artifact set
without writing.