Why does $.flow.trigger cause interference between similarly named steps in different workflows?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

I found a problem with $.flow.trigger
I have two workflows W1 and W2. W1 calls W2. I had the issue, that in the second workflow W2 a property from my step “prepareData” could not be read and was always undefined. But when I run W2 alone, everything works fine.

After investigating some time I found out. that both workflows had a step “prepareData”. The one in W1 didn’t have the property, the one in W2 has the property.I renamed the step in W1 and now the workflows work together. Looks like they access the steps of the other workflow if called by $.flow.trigger

2

Good call! I’ll add this to the troubleshooting docs

3

Thanks for sharing!

4

I’ll also try to reproduce and check with the team

5

Hey , I tried to repro but wasn’t able to — what is the workflow ID for W1 and W2?

6

and

in the second one you see also all the failed runs

7

Hmm yeah I see it

8

I think this is being tracked by the team btw

9

Steps with the same name in subflows got “overwritten”