This topic was automatically generated from Slack. You can find the original thread here.
hey all, i’m running into an issue with parallels. I test my workflow with all of the action steps outside of the parallel and it runs successfully, however when i pull my steps inside of a parallel the workflow does not run any of the steps under the parallel even though all conditions are met to run
Is that in a deployed workflow or while testing?
both
It sounds like it might be a memory issue within that execution branch, which is technically a “sub-workflow”. In the future we’ll likely expose execution controls (memory, timeout, concurrency, etc) for individual execution branches, but right now they use whatever the workflow has.
So for now you can try increasing the memory, then deploy the workflow, and run it again.
Build mode right now uses a slight different execution environment, so I think memory settings aren’t applied there, which is why I’m suggesting to deploy the workflow in order to confirm.
i’m getting the same error when testing the workflow live after i’ve deployed it, i’ll try increasing memory a bit more to see if that fixes it!
but wouldn’t the workflow fail outside of the parallel due to memory being exceeded?
No because in theory (if it is this issue), it’s the sub-flow that’s failing
This of course should be (and will be) somewhat abstracted from you in the future, but this is my current hunch
I ran into a similar issue on my end the other day
gotcha so just max out memory for now?
Hm okay, probably not memory then, definitely wouldn’t need that much. Maybe try slightly decreasing memory and increasing the timeout? I’ll forward this to eng right now also.
For sure want me to share the workflow I’d in question?
*id
Sure
Project ID: proj_ddsPDnd
Workflow id: local-dev-publish-image-to-socials-p_wOCdK25
Thanks
