Can't set local variables within parallel
@Gaurav Chadha
Hello everyone I've sent an in app request about this earlier today, but I wanted to share this here for the community as well since I think this is a more critical bug that affects everyone:
If you set a local variable within a parallel node it won't be set. If you log it directly after it will log "undefined". I tried this also in a clean new workflow.
5 Replies
AI Support Bot Information
<@112676328783802368> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
This issue seems like a bug related to setting local variables within a parallel node that aren't being initialized as expected. This kind of issue may not yet be addressed in the FAQ or documented fixes. It's best to follow up directly with the support team for BuildShip through your in-app support request. They will have the latest information and may provide a workaround or update relating to this particular bug.
BuildShip AI Support
Hi @Brian thanks for sharing this bug, we are now tracking on this, as a workaround mentioned by @Luis over email - you can workaround this by handling the part of your workflow outside of the Parallel node, which should unblock you. Setting and reading variables continue to work without any issues outside of a Parallel node.
I got rid of all parallel nodes, though it is still not working, because the same issue happens in a "branch" node. Can this be fixed asap? Or are there any news on this?
will update you by today with fix on this.