This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email firstname.lastname@example.org for assistance.
My preferred way of tacking this is a batch macro approach - you turn each workflow into a macro as suggested and they will become step in your process. You will create an arbitrary dependency between the steps (control parameter for your batch macro) to ensure that step 2 waits for step 1 to finish before it starts and so on.
An alternative approach would be to use one of the Runner macros from CReW macros however this not something I'd recommend for server deployment as these macros trigger instances of the Alteryx Engine outside of the simultaneous throughput allowed on the server.