invalid_analytics_function

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Function 'toUnixTimestamp' is not allowed",
    "status": 400,
    "title": "Bad Request",
    "type": "/errors/user/bad_request/invalid_analytics_function",
    "errors": []
  }
}

​

Likely causes

• You used toUnixTimestamp. The tables store milliseconds, so use toUnixTimestamp64Milli.
• You used a JSONExtract* variant other than JSONExtractString.
• You used a window function. They aren’t allowed.
• You used a table function such as url, file, or remote. These get their own message.

• Aggregates: count, sum, avg, min, max, any, groupArray, groupUniqArray, uniq, uniqExact, quantile.
• Date and time: now, now64, today, toDate, toDateTime, toDateTime64, the toStartOf* family from minute to year, date_trunc, formatDateTime, fromUnixTimestamp64Milli, toUnixTimestamp64Milli, and the toInterval* family.
• Strings: lower, upper, substring, concat, length, trim, startsWith, endsWith.
• JSON: JSONExtractString.
• Math: round, floor, ceil, abs.
• Conditionals: if, sumIf, countIf, case, coalesce.
• Conversions: toString, toInt32, toInt64, toFloat64.
• Arrays: has, hasAny, hasAll, arrayJoin, arrayFilter.

​

How to fix

1. Rewrite the expression with an allowed function: toUnixTimestamp64Milli for toUnixTimestamp, JSONExtractString for other JSONExtract* variants, and a GROUP BY with an aggregate instead of a window function.
2. If you need a function that’s missing, ask in Discord or open an issue.

​

Related errors

• err:user:bad_request:invalid_analytics_query: the query failed for another structural reason.
• err:user:bad_request:invalid_analytics_table: the query names a table that isn’t exposed.