AI troubleshooting
Why AI button is greyed out, why fallback model was used, why a suggestion looks wrong — common causes and fixes.
AI buttons are greyed out
Most likely your company has the AI toggle off on /recruit/company. Ask your owner or super-admin to enable AI Assistants in the Security & Settings panel.
- Symptom: button shows but click returns 403
- Other cause: form has missing required fields (e.g. country not selected for salary advisor)
- Other cause: the underlying AI service is degraded — wait a moment and retry
Salary range looks wildly off
The model is anchored on the country's local currency, but if the input is sparse it may default. To get accurate ranges, fill ALL the required fields before clicking: title, category, seniority, work mode, country and city.
JD output is too generic
The writer uses what you give it. Fill in your company's mission, the green category, seniority and a salary range before generating — these all anchor the language. You can also regenerate with different fields.
Fallback model was used
Internally we may log a "fallback used" flag on some calls — that just means the primary AI model briefly failed and the secondary picked it up. Output quality is essentially the same — no action needed on your side.
Token / quota concerns
GreenHired platform admins monitor company-level token consumption internally — if your company is hitting unusual usage, we'll reach out. Owners can also flip the org-wide AI toggle off at any time to throttle/stop usage.
Need something else?
Did this article miss the mark, or do you have a question we have not covered yet? The GreenHired team is happy to help.