Bug reportAug 24, 2026· 0:36· 13 views
Grafana Play: ?from=now-604800s silently falls back — time parser rejects 6-digit offsets
0:36 total
Comments · 0
Be the first to comment.
Bug report— by SceneRecap AI
mediumTimePicker / URL Range Parser
os: macOSbrowser: Chromium 151.0.7922.34viewport: 1280x720
Repro steps
- 1.Open Grafana dashboard (initially showing 'Last 7 days UTC' at 0.0s).
- 2.Navigate to a relative range such as Last 6 hours (observed loading successfully at 11.0s).
- 3.Open the Time range picker dropdown to inspect current range parameters (19.0s).
- 4.Navigate to the dashboard using a 6-digit second relative offset URL query parameter (?from=now-604800s at 24.17s).
- 5.Observe dashboard time range fallback behavior upon reload (27.0s-31.0s).
Expected
The time range parser should parse 'now-604800s' as a valid relative time offset (7 days) and apply it to the dashboard.
Actual
The 6-digit second offset query parameter fails to parse and silently falls back to the default time range ('Last 7 days UTC').
Evidence
visualWorking control: Navigating to Last 6 hours parses and displays 'Last 6 hours UTC' correctly at 11.0s.
visualTime range picker dropdown shows active quick range selection and custom range inputs at 19.0s.
visualAfter navigation with offset query parameter at 24.17s, the page reloads and silently reverts the picker to 'Last 7 days UTC' at 27.0s.
Issue markdown (copy-paste ready)
### Summary When navigating to a Grafana dashboard using a 6-digit second offset in the URL query parameter (such as `?from=now-604800s`), the relative time string is not parsed as expected and silently falls back to the default dashboard time range (`Last 7 days UTC`). ### Steps to Reproduce 1. Open a dashboard with standard time range controls. 2. Navigate with relative ranges (e.g., Last 6 hours works as expected). 3. Navigate to the dashboard with `?from=now-604800s`. 4. Check the displayed time range picker after the page loads. ### Expected Result The time parser should recognize `now-604800s` as a valid second-based relative offset and apply the corresponding range. ### Actual Result The parser fails to process the 6-digit second offset parameter and silently resets back to `Last 7 days UTC`. *Recorded with SceneRecap.*
Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →