Brian
Brian2w ago

Async task node

It would be great if we have a node that can encapsulate any other node and everything in there runs in a separate task asynchronously. This was previously only possible by calling a separate Workflow with the old version of the "Execute Workflow" node and you set "await" on false, but there we had to create a second workflow that makes everything more complex. And I think it would be the best to just have an encapsulation node for this case instead of adding an "await" parameter to every single node. Optionally this "Async Task" node can also have a parameter that declares what happens if the workflow breaks ("stop async task" OR "Keep running")
2 Replies
AI Support
AI Support2w ago
AI Support Bot Information
<@1227983829856157809> 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 Support
AI Support2w ago
AI Response
Currently, there isn't a specific "Async Task" node available that encapsulates other nodes to run them as separate asynchronous tasks within the same workflow. The traditional approach, as you mentioned, involves using the old "Execute Workflow" node with "await" set to false, creating a second workflow. While no dedicated node exists at the moment, it's a useful suggestion that could simplify workflow management. If it aligns with community interest, it might become a possibility in future BuildShip updates. For now, using the "Execute Workflow" node remains the method to handle components requiring asynchronous execution by connecting them to separate workflows.
BuildShip AI Support

Did you find this page helpful?