Concepts
Troubleshooting and help
Start with cady status --check --online: it tests sign-in, company, schedule and the server, and prints the fix beside each failure.
Exit codes
- 0: success.
- 1: the server refused the call, or a batch stopped after a refusal.
- 2: invalid input, or a write with an unconfirmed project company. Nothing was sent.
- 3: sign-in failed, or the call could not be verified. Check the record before retrying.
- 130: interrupted.
Sign-in fails or has expired
A connection needs a fresh sign-in every 90 days, and after 30 days unused. Scheduled agents hit the same limit.
Run cady local login to sign in again in your browser. cady local logout removes the saved sign-in.
The wrong company
Run cady local company show. See Choose a company.
Sync is not reporting
Run cady sync check, then cady sync --force to try once now. See Report usage.
Getting help
Email team@cadyworks.com with the command, its output and cady --version. Do not send tokens or sign-in codes. Signed in? Report an issue from app.cadyworks.com/support.
For agents: this page as Markdown.