Troubleshooting JAX

If JAX does not appear in the toolbar of the JAMS Web Client or the drawer shows an error, check the following:

Symptom	What to Check
Icon does not appear.	Hard-refresh the browser. The UI caches the disabled state for the session.
JAX drawer shows an error.	Call GET https://\<gateway\>/api/JAX/whoami as an authenticated user. If "enabled" is false, see Enabling JAX to enable JAX.
Service fails to start.	Check the service log at <JAMS install root>\JAX\logs\. Fix the validation errors listed and restart the JAX service. OptionsValidationException: Provider configuration is invalid. Fix every reported rule and restart. JAX is DISABLED near startup: JAX:Enabled is false in the settings.json. Update and refresh the browser. Provider_unauthorized on first turn: Wrong API key or wrong endpoint path. Verify if the provider expects "/v1" or "/openai/v1". Provider_bad_request referencing reasoning_content: Switch to a standard chat-tuned model or configure a LiteLLM proxy to disable thinking mode. Provider_quota_exceeded: Billing/quota. Update your billing or switch to a different model. Provider_rate_limited: The provider's per-account rate limit is below your sustained turn rate. Reduce turn frequency or request a quota increase from your provider.
Unauthorized error on first turn.	The API key is wrong or the endpoint path is incorrect. Verify the JAX__PROVIDER__APIKEY environment variable and restart the JAX service. See Enabling JAX.
Approval card expired.	Ask the question again to generate a new approval. See Using JAX.
Turn times out at 300 seconds.	The browser watchdog is 300 seconds and the server emits an SSE heartbeat every 30 seconds of idle time. If turns persistently time out, add/raise JAX:Limits:TurnTimeoutSeconds option. See JAX Overview.