I checked out your account and found the workflow you were referring to; I was not able to observe the issue you were describing as you had state messages coming in through the workflow.
Since I can’t actually edit your workflow, I also created this attached workflow, which recreates in a simplified fashion the part of the workflow where you described the problem, and couldn’t recreate the problem there, either.
Are you still seeing the issue you describe? And if so, is there a key difference I’m missing here when it comes to recreating the problem you’re seeing?
Finally, I see as you described that you have multiple versions of your workflow, but it appears the ‘develop’ version is currently the default. Workflow storage being shared across versions could be the cause of what you’re seeing, but do you actually have any payloads running through your 0.2 version?
vb-test-develop.flow (2.7 KB)