Why an action can be missing from the activity log

If an action you expect to see in the activity log shows nothing, the most common reason is that it happened outside your activity log retention window. Activity logs are viewable for a limited period, 30 days on premium plans, and anything older is hidden from the UI. The event itself is not lost. The record still exists; it is just past the window the interface displays. So an empty or incomplete log for an older action usually means the retention window has passed, not that the action went unrecorded.

How activity log retention works

Activity logs record actions taken in your organization, whether through the UI, via the API, or triggered automatically by the system, such as automated billing operations. Access is limited to paid tiers, and on premium the viewable history is up to 30 days. Once an event falls outside that window it no longer appears in the activity log view, even though it occurred and was logged.

This applies to any logged action, not any one type. Whether it is a void, a creation, an update, or a system-triggered change, the age of the event relative to your retention window is what determines visibility, not whether the event was captured. A recent action shows its details; the same kind of action from outside the window does not.

How to get details for an event outside the window

There are two paths when the event you need is older than your retention window.

Reach out to Lago. Retention can be extended beyond the default for some plans, and support can retrieve log entries older than your current window on request, so you are not stuck without an answer for a specific older event.

Keep in mind who the actor may be. The "who" behind a change is not always a person. Because the system itself can initiate actions like automated billing or correction jobs, an event may legitimately have been performed by the system rather than a user. In that case the actor shown, once the entry is retrieved, will reflect a system source.

This article reflects guidance drawn from customer case resolutions. It is not officially supported documentation and may not apply to all situations.