## What happened
Events POSTed to /api/v1/events were accepted (returned a lago_id) and visible in the developer events UI, but the current usage API kept returning events_count = 0 for a count_agg billable metric (code chat_number). Another user hit the same thing. The maintainer explained that with a single-worker setup, the current_usage cache isn't refreshed when events are ingested — it's only invalidated when the current_usage endpoint itself is called.
## The fix that worked
The events are being counted; the usage endpoint serves a cached value that isn't invalidated at ingestion time. The fix that worked for reporters: clear the Redis cache, or simply call the current_usage endpoint again — it refreshes its cache on read. Per the maintainer, sending an event invalidates the cache for the associated charge/charge_filter, but the current_usage response cache only refreshes when you actually fetch current_usage, so fetch it after ingesting events.