A webhook-triggered workflow is intermittently failing in Tables find-records filters with:
“Invalid input: expected string, received undefined”
The webhook body contains a valid body.run_id. I added a Code step immediately after the trigger to normalize body.run_id into a plain string output. Downstream Tables steps mapped to that normalized output still intermittently fail as if the mapped value is undefined.
This began after previously stable runs. Please investigate dynamic value resolution from webhook/code-step outputs into Tables filter values.