Running Steps Asynchronously with the Go Async ComponentLast Updated: 08/11/2016 Introduced in Verision: 2.0
The Go Async component allows subsequent flow steps to be run asynchronously, returning control immediately to the flow’s calling entity (such as a parent flow, user or process). In other words, any steps placed after the Go Async component will run autonomously.
The Go Async component can be found in the Toolbox panel, under the category Flow Management.
Our example flow will add a document containing a list of over 1,000 new subscriber email addresses to our process folder. Our flow will then send a welcome email to each one of those subscribers. Because the process of sending 1,000 emails will not return a necessary output, and because the process itself could take a very long time, we will make it happen autonomously with the Go Async component.
Our example flow has already been started with some functional components already in place. We will continue building it by going to our Designer Folder and clicking the Edit link on the Go Async Flow thumbnail.
In the Flow Designer, notice that the steps already in place are Email Address List (which provides the list of subscriber email addresses) and Send Email 1 (which will send welcome emails to those addresses). Both steps are configured and ready to go, except for the fact that they are unconnected.
After our example flow adds the list of email addresses to our process folder, we want it to begin autonomously sending the welcome emails, and immediately return control to the entity that called it. In this case, returning control to the entity is equivalent to immediately progressing to the End Step while Send Email 1 continues to send emails.
To do this, place the Go Async component in the flow between Email Address List and Send Email 1. It is in the Toolbox panel, under the category Flow Management.
Next, connect Email Address List to Go Async 1, and Go Async 1 to Send Email 1 with their respective Done outcomes.
This completes our flow. To debug it, click the Debug Flow link at the top of the Flow Designer.
Note that in Decisions version 3.5 and above, you’ll need to click on Test Flow to access the Debugger.
Our example flow progresses smoothly to Send Email 1 a step that ordinarily would take several minutes
but, in this case, continues asynchronously while our flow continues uninterrupted to the End Step.