Troubleshoot Jama Intelligence Gateway
Identify likely causes and checks for Jama Intelligence Gateway configuration, connectivity, and response errors.
Symptom | Likely cause | What to check |
|---|---|---|
Assistant isn't available and a adapter URL isn't saved | The organization isn't configured | Save a valid complete adapter URL and confirm that Assistant is enabled. |
The adapter URL can't be saved | The URL is invalid | Use an absolute HTTP or HTTPS URL, include the host and complete operation path, and remove embedded user information. |
Jama Connect can't reach the adapter | DNS, route, TLS, firewall, timeout, or adapter availability | From the Jama Connect environment, verify name resolution, routing, certificate trust, port, and adapter health. |
401 or 403 | An endpoint, proxy, gateway, or provider access policy rejected the request | Jama Connect doesn’t send an adapter authorization header. Check whether the endpoint requires credentials or identity the client cannot provide. |
404 | The configured operation path is incorrect | Save the complete POST operation URL. Jama Connect doesn't append an adapter path. |
429 | The adapter or provider is throttling requests | Check provider quota, concurrency, retry policy, and adapter limits. |
400, 422, or an incompatible-response message | The request or response doesn’t match the Jama Intelligence Gateway adapter format | Confirm contractVersion: 1, required fields, field names, roles, message parts, tool identifiers, arguments, and endTurn. |
500, 502, or 503 | Adapter configuration, adapter runtime, or provider invocation failed | Inspect sanitized adapter logs and provider status. Confirm the model/deployment, region, credentials, quota, and provider endpoint. |
Assistant adapter update required | The endpoint responded, but its response isn’t compatible with Jama Connect | Confirm that the URL identifies a Jama Intelligence Gateway-compatible translation endpoint. A direct provider API or unconfigured pass-through proxy is not sufficient. A programmable proxy or gateway can be used when it performs the required request and response mappings. |
A basic answer works but Jama Connect tools fail | The model or adapter can't complete the tool workflow | Test tool definitions, forced-tool selection, structured arguments, identifiers, tool-result correlation, provider role conversion, and continuation. |
A prompt change isn't visible | The test reused an open conversation, the save did not persist, or replicas use different storage | Start a new conversation. If the change is still absent, check the save result and /config persistence. For multiple replicas, confirm shared RWX storage. |
Prompt behavior differs between replicas | Prompt storage isn't shared | Configure every Assistive AI replica to use the same RWX volume. |