## TL;DR

Check that the workers are healthy, then query current_usage again to rebuild the cache. Newer Lago versions compute usage from the last ingested event time instead of the old refresh-on-ingest behavior. Maintainers explained the current_usage response is cached: ingesting an event invalidates that cache in the background, which only happens when the lago-worker is up and running, and the cache is rebuilt the next time current_usage is queried.

## Fix

When Lago ingests events but current_usage still shows zero, suspect the usage cache, not the events. Event ingestion invalidates the cached usage in the background, so if lago-worker is not running the cache never refreshes and your counts look stuck. Check that the workers are healthy, then query current_usage again to rebuild the cache. Newer Lago versions compute usage from the last ingested event time instead of the old refresh-on-ingest behavior.

Context: GitHub issue getlago/lago#538 (closed): Events were ingested successfully and visible in the developer events UI, but the current_usage API kept returning events_count = 0. Maintainers explained the current_usage response is cached: ingesting an event invalidates that cache in the background, which only happens when the lago-worker is up and running, and the cache is rebuilt the next time current_usage is queried. The issue was closed after the cache management was refactored so usage is computed based on the last received event time.

## Matched source
Source: Published skill
Original query: "Lago events ingested but usage shows zero: the usage cache needs the worker"
Key terms: cache, events, ingested, lago, needs, shows, usage, worker, zero

## When to use this

- Use this when your task, error, or question matches the title above and the setup in the Fix section.

## When not to use this

- Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

## Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.
