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.
Do you use Alteryx in a language other than English? If so, we want to hear from you! Please help us improve the international experience of our products by participating in this 5 minute survey.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
When we run the Alteryx CREW macro on the Server, I am aware of the part mentioned in some threads wherein it keeps the thread open and the controller has no control over it which may lead to memory leaks and causing performance issues. However I want to know when there are 20-30 workflows configured in a master workflow which calls another workflow through the "Conditional Runner" so I know it runs the workflow sequentially instead of running them in parallel. By any chance is it that even if workflow number 1 ran successfully and did its job when the workflow number 3 is running the tool level or output data generated data at workflow number 1 will still be stored in the system memory or is it that when workflow number 3 is running the memory used to store the runtime data for workflow number 1 is released from the memory?
The CReW macros are a useful collection of tools built by a third party that enhance the functionality of Alteryx Designer.
The CReW Runner macros (Runner, Conditional Runner and List Runner) are the only CReW macros supported by Alteryx, but for Alteryx Designer ONLY. These macros are not supported when used on Alteryx Server, Alteryx Designer + Scheduler or AAH.