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.
A user might want to schedule a workflow to run each day at 7:30 AM; however, the workflow takes approximately 30 minutes to run, and the data may not always be available by 7:30. To avoid rescheduling the time-consuming workflow, it is more efficient to have a smaller workflow that checks the database to ensure the data is up to date, and then executes the main workflow when the given criteria have been met.
This can be accomplished with a Test tool from the Developer category, and a workflow event.
The following is an example of a simple logical test used to determine whether or not to kick off the main workflow. If the two input dates equal each other the test workflow will return an error.
By selecting the "Events" tab and Adding a Run Command the event can be configured to begin another process upon successful completion of this module. Configuration guidelines are:
Run Event When - Choose "After Run Without Errors" Command - Select the AlteryxEngineCmd.exe which is usually located at "C:\Program Files\Alteryx\Engine\AlteryxEngineCmd.exe" depending on your installation
Command Arguments [Optional] - Navigate to the module you wish to schedule upon successful completion of this module. (NOTE: the filepath and module name must not have any spaces to work properly)
By scheduling the smaller test workflow at a certain time interval (e.g., every 10 minutes) for a given period of time each day of the week, the larger and more complex workflow will only execute upon the successful completion of the basic module, saving processing time and the need to re-run a complex module.