Skip to main content

Jama Connect Help

Collect Jama Intelligence Gateway Diagnostics

If Jama Intelligence Gateway has an issue, gather the error, workflow, and log details needed to investigate it. Follow the guidance for your deployment method.

Collect diagnostic information

Before submitting a Support ticket, record:

  • Jama Connect version and build.

  • Deployment method: Jama Connect KOTS or Kubernetes-Native.

  • Incident timestamp and time zone.

  • Whether the issue affects all users or one organization/user.

  • The first failing step: opening Assistant, basic response, tool request, tool result, confirmation, or final response.

  • The exact Jama Connect message and HTTP classification.

  • Whether the deterministic adapter works.

  • Adapter build/version and recent adapter, provider, or model changes.

  • Sanitized Assistive AI, adapter, gateway, and provider logs.

Never include provider secrets, access tokens, private keys, session cookies, or raw sensitive customer content in a ticket.

Jama Connect KOTS diagnostics

Generate deployment diagnostics and the standard support bundle from the KOTS Admin Console. The System health report monitors high-volume product areas; it does not report Assistive AI pod, service, or persistent-volume health.

Review and redact the support bundle before transfer.

Jama Connect Kubernetes-Native diagnostics

Use the approved version of the Kubernetes customer toolkit or your standard Kubernetes diagnostics. Limit collection to the affected namespace and incident window when possible.

Review and redact internal host names, IP addresses, tokens, secrets, credentials, provider responses, prompts, and customer content before transfer.