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.
Hi @amitbanwar! What is your use case here? Since you have the alteryx server, it seems like the gallery would be the way to go. That would allow you to schedule a job every minute. I'm not sure what would happen if it took longer than 1 minute, I'm partly guessing, but I think the gallery would just wait to fire the next job until the first one completes.
I found this post that may help you get to this frequency. Basically, you'd have an iterative macro that's iterating every 5 secs to do the file check. The calling workflow would be always running to allow the file check to continuously occur.
You could provide the number of iterations for 1 minute (60 secs / 5 secs = 12 iterations), then schedule it to run every minute on the server. So you'll wind up with continuous checking over many individual workflow executions.
Hi @amitbanwar , I also wanted to mention, from an Alteryx Server resource perspective it is not recommended to run workflows outside of the Alteryx Service/Gallery environment. Workflows run through the Alteryx Gallery and Scheduler use a queuing process to help maintain a balance of the number of workflows running at any given time (workflows allowed to run simultaneously) and the available system resources (RAM and CPU) to allow for workflow execution and to reserve enough resources for the operating system.
Workflows that are run via command line on the Alteryx Server are run outside of the queuing process and would be additional load on the server resources. For example if the server is configured to run 4 workflows at any given time (based on server resources), between manually executed and scheduled jobs, and then a workflow is run through the command line, there will be 5 workflows running at once and my put a strain on the server resources.