Help
Troubleshooting
Real messages Headwind shows, what causes them and how to fix them.
Common problems
“No password is set for this Headwind install.”
- Likely cause
- HEADWIND_PASSWORD is empty.
- How to check
- Look in the server's environment file.
- How to fix
- Set it and restart the web app.
“Too many wrong passwords.”
- Likely cause
- Five wrong attempts from your address.
- How to check
- Wait for the message to clear.
- How to fix
- Try again after 15 minutes.
Review stays on “Waiting for the worker”
- Likely cause
- The worker isn't running.
- How to check
- systemctl status headwind-worker on the server, or npm run worker locally.
- How to fix
- Start or restart the worker. The queued review is picked up.
“Crustdata budget for this review is used up.”
- Likely cause
- The review hit its credit budget.
- How to check
- The Overview shows credits used.
- How to fix
- Finished steps are kept. Retry unfinished steps once you're happy to spend more credits.
“The imported data changed after this review was planned.”
- Likely cause
- You imported after the review was queued.
- How to check
- Compare the import time with the review start.
- How to fix
- Start a new review.
“cfo.ai sign-in expired and could not be renewed.”
- Likely cause
- The cfo.ai token can't be refreshed.
- How to check
- The review shows the sync step stopped.
- How to fix
- Reconnect cfo.ai, then retry unfinished steps. Earlier steps aren't repeated.
“cfo.ai isn't set up for this agency yet.”
- Likely cause
- No Reviewed/Downside scenarios are linked.
- How to check
- Run the setup script.
- How to fix
- npx tsx scripts/cfo-setup.ts, then retry.
Role shows “Company match: more than one possible company”
- Likely cause
- Crustdata returned several companies for that domain.
- How to check
- Open the role's evidence.
- How to fix
- Nothing breaks: the role relies on agency records and client replies. Confirming a match by hand isn't supported yet.