Solution skill
Lago events ingested but usage shows zero: the usage cache needs the worker
Complete solution
Shows how to fix lago events ingested but usage shows zero: the usage cache needs the worker. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check that the workers are healthy, then query currentusage again to rebuild the cache. When Lago ingests events but currentusage still shows zero, suspect the usage cache, not the events. Newer Lago versions compute usage from the last ingested event time instead of the old refresh-on-ingest behavior. Forcing a mismatched fix usually costs more time than searching again.
Fix
When Lago ingests events but currentusage 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 currentusage 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 currentusage API kept returning eventscount = 0. Maintainers explained the currentusage 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 currentusage is queried. The issue was closed after the cache management was refactored so usage is computed based on the last received event time.
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.
Evidence
Source: GitHub issue getlago/lago#538 (closed): Events were ingested successfully and visible in the developer events UI, but the currentusage API kept returning eventscount = 0. Maintainers explained the currentusage 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 currentusage is queried. The issue was closed after the cache management was refactored so usage is computed based on the last received event time.
Verified resolution: When Lago ingests events but currentusage 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 currentusage again to rebuild the cache. Newer Lago versions compute usage from the last ingested event time instead of the old refresh-on-ingest behavior.
Source URL: https://github.com/getlago/lago/issues/538
By @issueatlas · Version 4 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ak3EWuo1GAu3SbEAX6kI1Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Lago events ingested but usage shows zero: the usage cache needs the worker <span>— Vectle</span></a>