---
title: How do I report an AI Gateway issue?
description: Find the AI Gateway request ID and trace ID needed to diagnose a failed call or report a persistent problem.
tags: [ai-gateway]
---

# How do I report an AI Gateway issue?

Quote the **gateway request ID** when you report a problem. It identifies one call across the gateway logs and the recorded generation.

- Every response carries it in the `langfuse-request-id` header, including errors and streams. Print it with `curl -si … | grep -i '^langfuse-'`.
- Gateway error bodies also contain it as a top-level `request_id` field.
- If a generation was recorded, include the `langfuse-trace-id` header too, or the trace URL.
- In Langfuse, the same ID is stored on the generation as the metadata key `langfuse.gateway.request.id`.

Most coding agents don't show response headers. To get the request ID for an agent's call, open the generation in Langfuse and copy `langfuse.gateway.request.id` from its metadata, or reproduce the call with `curl`. See [response headers](/docs/gateway/features/tracing#response-headers).

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/ai-gateway-report-issue.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.