---
title: Missing events after POST /api/public/ingestion in self-hosted Langfuse
seoTitle: "Missing Events After Posting to the Ingestion API"
description: "Events posted to /api/public/ingestion but never appearing on self-hosted Langfuse: how the async pipeline works and where to look for the failure."
tags: [self-hosting]
---

# Missing events after POST /api/public/ingestion in self-hosted Langfuse

If you are not seeing events within minutes of posting them to `/api/public/ingestion`, it is likely that the events are not being ingested correctly.
Events do not appear immediately in the UI, as they are being processed asynchronously.
If your events are not shown after a few minutes, you can check the following:

- **Check the Langfuse Web logs**: Look for any errors in the Langfuse Web container around the time that you ingested the events.
  Any errors you observe indicate that the event is malformatted or that either [Redis](/self-hosting/deployment/infrastructure/cache) or [S3](/self-hosting/deployment/infrastructure/blobstorage) are not available.
  In this case, you should also see non-207 status codes within your application.
- **Check the S3/Blob Storage bucket**: Validate that the event was uploaded correctly into your blob storage.
  It should be available in a path like `/<projectId>/<type>/<eventId>/<randomId>.json`.
  If the event was accepted in the Langfuse Web container, but is not available in S3, it indicates an issue with your S3 configuration.
- **Check the Langfuse Worker logs**: Look for any errors in the Langfuse Worker container about within 0-60 seconds of ingesting your event.
  If no events at all are being processed, it usually indicates a configuration issue around Redis or S3.
- **Check ClickHouse tables**: If the previous processing looks correct, validate whether you can find the event in ClickHouse in the `traces`, `observations`, or `scores` table.
  Search for the respective `projectId` and `eventId`.
  If you cannot find the event in ClickHouse, but the worker indicates it was processed or if you can find it in ClickHouse and it is not returned via the API, please [open an issue](https://github.com/langfuse/langfuse/issues).

<!-- 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/self-hosting-missing-events-after-ingestion.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>.