Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
SOLVED

Schedule a report to run every other Monday

JasonJaworski
6 - Meteoroid

Does anyone know of a way in server to schedule a report to run every other Monday? The closest I can see is to set up two monthly schedules on that runs on the first Monday and one that runs on the third Monday but that still does not consistently run the report every other Monday.

5 REPLIES 5
cpet13
11 - Bolide

@JasonJaworski something you could do is set a schedule to run on a recurring basis with the frequency set to hourly, then have the hours set to 336 (or two weeks). Then set the start date to be on a Monday.

Screenshot 2024-09-13 140222.png

JasonJaworski
6 - Meteoroid

@cpet13  Thanks for the suggestion. We will give this a try!

fmvizcaino
17 - Castor
17 - Castor

Very clever @cpet13 , thanks for sharing it!

ColinG
7 - Meteor

Does anyone else have issues when the Alteryx server is busy that subsequent runs happen on the schedule X hours after the immediate last run - not based on the original schedule? So if it first ran at 8 am, and 2 weeks later it runs at 10 am due to load, then 4 weeks later it runs at 10 am or after. Our Alteryx server at times will be busy enough that a run happens an hour or 2 late. Over several months on a busy server, I could see this pushing into Tuesday and on, unless it's closely watched.

Another option our Team has done is inside a workflow near the beginning we put a filter tool - connect data output only to T and leave F unconnected. The server schedule would run every Monday. But the filter tool would be set to be true if the week number was an even number. So on odd numbered weeks the condition would be false and the run quickly ends on server after providing no output.


cpet13
11 - Bolide

@ColinG thanks for your insight. I can see how that might cause an issue. That is a good suggestion. Another is to use the Priority option when scheduling the workflow. Set this workflow to have a priority of Critical, meaning that if there is a buildup of workflows waiting to be run, those with a priority listed as Critical will run first. That would help alleviate the problem, though I'm sure it would not be a perfect solution - depending on the number of jobs an organization has, if they are using the Priority option for those other jobs and have marked many as Critical already, etc.