Following up because this remains production-blocking. I love activepieces and am unable to do any work on my workflows because of this issue. Please help!
I still have no response on:
The issue appears aligned with PR #13571:
“Data mapping between steps is broken on main for many existing flows.”
Please confirm:
- Has PR #13571 been merged?
- Has it been deployed to cloud.activepieces.com?
- Does the fix repair existing affected flows, or only newly published flows?
- Is the cloud publish bug that appends/nests [‘output’] into tokens resolved?
- Should affected users avoid publishing until this is fixed?
- Can engineering inspect my affected flow, since duplicating the flow did not repair it?
This is currently blocking production execution because dynamic mappings from webhook/code/table steps intermittently resolve as undefined/empty while hard-coded values work.