Retool GUI insert suddenly failing for BigQuery DATE column (was working before)

💬 Queries and Resources
1

Hi,

I'm using Retool GUI mode to insert records into a BigQuery table.

Recently the insert started failing, even though nothing in the app or query was changed.
Previously this worked without any issues.

The BigQuery column type is DATE.

In the GUI mapping I use the following expression to allow null values:

{{ some_date_field.value ? some_date_field.value : { RT$BQ_TYPE: 'date', value: null } }}

However the generated query looks like this:

insert into `dataset.table`
(..., some_date_column, ...)
values (..., '{"RT$BQ_TYPE":"DATE","value":null}', ...)

And BigQuery returns this error:

Invalid date: '{"RT$BQ_TYPE":"DATE","value":null}'

What is confusing is that this used to work before and suddenly stopped working, even though no changes were made to the query or the mapping.

Has anyone experienced this with Retool GUI insert + BigQuery DATE columns?

Is there a recommended way to handle nullable DATE fields when using Retool GUI mode?

Thanks!

1 Like
4

Having this same issue. No changes made but having issues across various apps and implementation types now. After going through all of my logs I was able to pinpoint my first failed job on one query to

First failure: 2026-03-12T03:12:23 UTC
Last success: 2026-03-11T02:17:43 UTC

Sometime between those two timestamp some update seems to have been made causing this failure. Looking through my logs further I noticed on the bigquery side there is a change in how my “named parameters” are showing. For my specific implementation I used to get @=23791571792 which worked well, now I see @={"RT$BQ_TYPE":"INT64","value":23791571792} which is causing errors.

I seem to have fixed this by changing what used to exist on the retool query field

"value":"{{ {RT$BQ_TYPE: \'INT64\', value: ProductEnrichmentForm.data.product_id }}"}

To now not have the bigquery type

"value":"{{ ProductEnrichmentForm.data.product_id }}"}

But as the initial post says, I have not changed anything on my apps related to these update queries in a long time. I don’t remember why I had this one specific field setup to insert with {RT$BQ_TYPE: \'INT64\',.... but not on my other fields. So the real question might be, was there a bug that got patched now causing my workaround to fail, OR is this a new bug.

1 Like
5

Hi @avi ,

We recently made a change that has since been disabled for all Cloud users that should have fixed this issue. Can you confirm that your BigQuery resource is now working again?

6

Thanks for checking.

I was able to confirm that saving works on my side now as well.

For now, the issue seems to be resolved, although I'm not sure what exactly caused it.
In my case, switching to SQL mode also worked as a workaround.

Appreciate your help!