Skip to main content

​
Access or authentication fails

Confirm the API key and complete endpoint URL belong to the same deployment. SDKs use the classify URL. LiteLLM uses the supplied guardrail URL. Check authentication responses for the status returned by your deployment path.

​
Traffic is missing

Check the selected Firewall, region, and dashboard time window. Record the timestamp and request ID from a new test request. Confirm that execution uses the configured client, wrapped model, proxy, or protected agent session. Follow verification for the integration you installed.

​
A call fails

An API or transport failure leaves the request without a verdict. Apply the boundary’s configured failure policy and retain the status code and request ID for review. Use your SDK’s documented retry and cancellation behavior. Retry model or tool operations only when the application can safely repeat them.

​
Request body timeout

The direct Firewall runtime returns HTTP 408 with code request_body_timeout when receiving the request body exceeds its deadline. It closes the connection before classification runs, so the response contains no verdict. Python and Go intentionally retry HTTP 408 by default. Python callers can configure max_retries (set it to 0 to disable retries); Go callers can use context cancellation or deadlines to bound retrying. The TypeScript SDK retries HTTP 429 only and surfaces 408 as an API error. A final API error means no verdict was returned to the caller. Retrying this pre-classification request does not establish that replaying an arbitrary model or tool operation is safe. Apply your application’s fail-open or fail-closed policy when the SDK returns an error.

​
Review compatibility fails

Check that the client meets the minimum SDK version. An explicit selection requires a matching top-level acknowledgement. Retain the requested and returned values when reporting a compatibility error.

​
A legitimate request is blocked

Inspect the prediction, optional governance decision, effective mode, and connected boundary. Report the finding with the authorized task and expected behavior.

​
Get support

Open Support in your dashboard and select the affected Firewall. Include the integration and SDK version, timestamp, request or finding ID, status code, and a sanitized description of the problem. For initial access, book a call. For local coding-agent setup and managed policy, use macOS troubleshooting.