Sasha Bratyshkin
02/25/2026, 6:47 PM{
"title": "Bad Request",
"status": 400,
"detail": "An error has occurred while calculating the result",
"resultId": "79c082dd3e7dafe73666573f8cce65c9a4a9d49b",
"reason": "General error",
"traceId": "ef266f9b6e47d44754793d706c602b72"
}
"General error" is a very generic error message. this happens when I add a specific field called [Profile field] Gender for this workspacekapa.ai
02/25/2026, 6:47 PMMauricio Cabezas
02/25/2026, 6:50 PMSasha Bratyshkin
02/25/2026, 6:50 PMMauricio Cabezas
02/25/2026, 7:09 PM"msg": "Execution of SQL statement has failed",
...
Caused by: net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error: error line 2 at position 485\ninvalid identifier '\"t15\".\"gender_[155]
The error it’s coming from Snowflake: the query is using a column that doesn’t exist (or has a bad name). Specifically, something like "t15"."gender_[155]" is being referenced, and Snowflake is rejecting it as an invalid identifier.
Please, make sure the Gender profile field is mapped to the actual column name in your Snowflake table (e.g. gender or whatever the real column is), not to something like gender_[155].
Once that mapping matches the real column, the error should go away.Mauricio Cabezas
03/02/2026, 12:57 PM