invalid_analytics_query

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Analytics queries must contain exactly one statement",
    "status": 400,
    "title": "Bad Request",
    "type": "/errors/user/bad_request/invalid_analytics_query",
    "errors": []
  }
}

​

Likely causes

• More than one statement, separated by ;, or no statement at all.
• SELECT *, or a column that isn’t exposed. The message says the column isn’t available.
• A SETTINGS clause, often pasted from a console session, such as SETTINGS max_threads = 4.
• A syntax error, or no FROM clause.
• An IN that reads from a table, such as IN (SELECT ... FROM table).
• The query is too big: more than 64 selected columns, more than 16 KiB of text, or more than 2000 syntax tree nodes (Analytics query is too complex).
• The query failed while running, for example on an unknown column (Unknown identifier), a type mismatch, or a division by zero.

​

How to fix

1. Send exactly one SELECT with a FROM, using only the documented columns of the analytics tables.
2. Remove SETTINGS.
3. Replace an IN (SELECT ... FROM table) with a literal list or a CTE.
4. For Unknown identifier, check the spelling and any CTE aliases.
5. Keep the query under 16 KiB and 64 output columns.

​

Related errors

• err:user:bad_request:invalid_analytics_table: the query names a table that isn’t exposed.
• err:user:bad_request:invalid_analytics_function: the query calls a function outside the allowlist.
• err:user:bad_request:invalid_analytics_query_type: the statement isn’t a SELECT.
• err:user:bad_request:query_range_exceeds_retention: the time filter reaches past the workspace’s retention window.