Agents use an in-memory leaky bucket buffer to hold events temporarily when the manager is unavailable. By default this client-side buffer holds up to 5,000 events and sends them at a throttled rate (500 events/second) to avoid flooding the manager.
If the manager goes offline, the agent will attempt to reconnect. Any events already in the buffer remain queued and will be sent once connectivity is restored.
However, no new events are added to the buffer while the agent is disconnected. This means the agent effectively stops forwarding additional logs during the downtime once the current queue is drained or full. This design prevents unbounded resource usage on the endpoint, it avoids writing huge log queues to disk or using excessive memory, favoring lightweight operation.
Here you can see the documentation about the buffer.