Phantom Metadata

[patient_but_frustrated]

The screenshot shows an output error caused by a 'post to resource' query. This query has run happily for at least two months and now does not complete.

The obscured credentials enable a connection to a public Supabase storage bucket. fileInput1 is a file browser box and its value is according to the structure 'filename', 'filetype', 'base64Data'.

The format of the data is only visible now because I have the error shown, but, as I say, the query has been happy and successful until now, both in Retool and Supabase. It appears as though Retool has suddenly started to include metadata in the output and that Supabase is not expecting this class of information and has no place to put it.

As always, any and all suggestions are very welcome.

[Darren]

Hey @patient_but_frustrated - thanks for reaching out.

Looking at our code base, it doesn't seem that user_metadata is being added to the query on the Retool side. You can verify this by checking the "Network" tab in your browser's dev tools when attempting to run the query.

Nonetheless, something has obviously changed if it's no longer working. I spun up a new Supabase project and it looks like the default objects table now has a user_metadata field.

You will probably want to write a migration to update the name of that column!