Running Steps Asynchronously with the Go Async Step
- 22 Dec 2023
- 1 Minute to read
- Print
- DarkLight
Running Steps Asynchronously with the Go Async Step
- Updated on 22 Dec 2023
- 1 Minute to read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Example Lab Article
While Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.
Overview
Example Lab Details | |
| Version | 8.4.0 |
| Root Folder | Go Async Email Example |
| Modules | None |
| Dependencies | None |
The Go Async step allows subsequent steps to run on a different thread and then returns control to the calling entity (parent Flow, user, or process). Steps that produce outputs will not be available to the calling entity since that entity will not have any insight into what that step is doing.
Explanation
The example Flow utilizes Run Flows for the List step with defined email addresses. Because the process of sending many emails will not return a necessary Output, and because the process itself could take a very long time, the process will run autonomously with the Go Async step.
Reference Articles
Project Download
The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production-quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on version 8.4.0 or later using our Importing/Exporting article.
Was this article helpful?
