Goal: I have a form that sends formData from a formData variable to a Retool workflow and also sends it in the body of a retool email. Suddenly, last night it started sending null values for all the input field values. When I test filling out the form, the values are not null, but then they get sent as null in both the workflow and retool email. This is for a public app page. Update: when I am logged in and submitting a form in the Retool, the values are not null. When I go on the user-facing public page, things become null.
This is quite urgent, as I have clients with their own customers that are trying to submit bookings and cannot.
Steps: I tried adding the email to capture the data as a workaround, but it fails too. I'm at a bit of a loss for what else to do.
Details: Using a formData variable, and formData.value is being passed into the Retool workflow and email.
Example:
When I look at {{ formData.value }} -- event_date is null. But when I hover over the value of formData, I can see that event_date properly reflects the input field's value.
Yes, it definitely could be as we ran into this issue while troubleshooting the overall null values getting passed in -- I just wasn't sure exactly how. No form data would be in the start trigger payload of the workflow (the start trigger data was just undefined), and so the workflow would just run whatever the test json was in the start trigger block.
Originally, changing from triggering the workflow via the Retool Workflow resource query did not work, and so we tried triggering the retool workflow via rest API with its endpoint. Initially that was also passing null values, but is working now -- so this works for us as a solution and we can consider this resolved!
