err:user:bad_request:query_range_exceeds_retentiondetail gives the earliest date you can query and the date you asked for.
Example response
Likely causes
- The lower bound on
time(with>,>=,=, orBETWEEN) goes back further than your plan’s retention.
today(), or now() with INTERVAL N UNIT, such as now() - INTERVAL 90 DAY. A bound written another way, such as toIntervalDay(90), or no lower bound at all, isn’t rejected. The query runs, and rows older than your retention are left out without an error.
How to fix
- Move the lower bound to the date in
detailor later. - If you need older data, move to a plan with longer retention. See Limits.
- To keep data long-term, schedule exports that run inside the retention window.
Related errors
err:user:bad_request:invalid_analytics_query: the query failed for another structural reason.err:user:too_many_requests:query_quota_exceeded: the workspace used up its analytics query quota.