This is not isolated to one step. A previously stable workflow began intermittently failing after no intentional changes to the affected lookup steps.
Failure pattern:
- Tables filters receive “Invalid input: expected string, received undefined”
- The webhook body contains a valid run_id
- Hard-coded filter values work
- Dynamic mappings from trigger/code-step outputs intermittently resolve as undefined
- Code-step inputs mapped from prior Tables steps sometimes arrive empty even when the upstream step returns rows
- Logging out/in and remapping did not reliably fix it
Please investigate whether dynamic value resolution, step output references, or workflow editor/runtime context changed recently for Tables v0.3.0 and Code steps.