Service log viewer misses recent historical logs but shows new live logs

Easypanel version: 2.35.0 Docker logging driver: json-file Log options: max-size=10m, max-file=3

There appears to be a bug in the standard service log viewer where recent historical log entries are missing when the Logs panel is opened.

Example: On September 17, opening the service Logs panel showed September 14 as the latest existing log entry.

However, Docker already contained log entries from September 15, September 16, and September 17.

Running: docker service logs --since 30m <service> or: docker service logs -f <service> shows those entries correctly.

An important detail is that live streaming works: if a new application event happens while the Easypanel Logs page is already open, that new log entry appears immediately; but the historical entries between September 14 and the moment when the page was opened remain missing.

the WebSocket inspection: /ws/serviceLogs?service=<service>&compose=false confirmed that the server sends log entries from September 15 and September 16 as part of the initial WebSocket data.

Nevertheless, those entries are not displayed in the log viewer UI. This suggests that the issue may be in the frontend handling or truncation of the initial log backlog rather than in Docker or the live WebSocket stream.

Expected behavior When opening the Logs panel, Easypanel should display the most recent existing log entries up to the current moment, and then continue appending new entries live.

Actual behavior The viewer displays older historical logs, skips a block of more recent existing logs, and then starts displaying only new entries generated after the page was opened.

Steps to reproduce

1. Use a service with several days of existing Docker logs.
2. Generate logs over multiple days.
3. Open the Easypanel service Logs panel.
4. Compare the latest visible historical entry with docker service logs.
5. Observe that some recent historical entries are missing.
6. Keep the Logs page open and generate a new log entry.
7. Observe that the new live entry appears correctly despite the historical gap.

It looks like the initial backlog is being truncated or rendered incorrectly, while the subsequent live stream works as expected.