Publishing a flow in the cloud appends ['output']

Need help
1

There is a critical bug when publishing a flow in the cloud version. Every time I click ‘Publish Flow’, the platform appends an extra ['output'] string into existing data tokens (e.g., turning {{trigger.data}} into {{trigger['output']['data']}}). If I publish 3 times, it nests it 3 times. This happens automatically to all pieces in the flow without modifying them. This happens with Firefox as well as with the ZEN Browser. So it is not a browser issue. It seams not to happen with the first publish. the work around is to export the flow, delete all ['output']import it again.

2

Hi @ManfredWahl

Escalated to the engineering team, They are taking look right now.

3

please don’t delete the flow you created, and please send us the flow you were using, was it this ?

4

also can you please confirm what is the url you are using ? it was cloud.activepieces.com and NOT canary.activepieces.com

5

This appears to match Activepieces PR #13571:

“Data mapping between steps is broken on main for many existing flows — even with small payloads.”

Our symptoms:

  • Previously stable webhook-triggered flow began failing without intentional lookup-step changes.
  • Webhook body contains valid body.run_id.
  • Hard-coded Tables filters work.
  • Dynamic mappings from webhook/code-step outputs resolve as undefined/empty.
  • Code-step inputs mapped from prior Tables outputs sometimes arrive empty even when upstream step returns rows.
  • Duplicating the flow did not repair the issue.
  • Tables Find Records fails with: “Invalid input: expected string, received undefined.”

Please confirm whether our cloud workspace/flow has been affected by the v22 step-output-nesting migration or the cloud publish bug that appends/nests [‘output’] into tokens.

Please also advise whether we should:

  1. wait for the engine fix to deploy,
  2. export/import after the fix,
  3. manually rewrite mappings to the new {{step.output…}} form, or
  4. avoid publishing until the cloud publish token mutation bug is resolved.
6

I am on cloud.activepieces

7

yes - it is cloud.activepieces.com. Nevertheless the issue is resolved. It seams that there has been an software update over the weekend, which caused many issues. Now the cloud version is fine again.

8

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.