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.
Upgrading Server to version 22.1? We’ve enabled the faster AMP engine by default. Read about how these system settings changes might affect you.
2022-05-24 Updates: Login: If you are facing issues with logging in, please try clearing all your cookies or trying another browser. We have a fix being deployed on the evening of 5/25. Email: If you're not seeing emails be delivered from the Community, please check your spam and mark the Community emails as not junk. Thank you for your patience.
With an Alteryx user workflow on the server, the schedule is moving from active to complete, even though though the end date is blank and never is also selected. Below is a picture of the schedule that is moving to complete
@mehtas0311 - any jobs that are queued up to run while your AlteryxService is in a 'stopping' state will automatically get marked as complete.
For example, you initiate a backup at 10:00pm, but there are some workflows actively running. The AlteryxService won't be fully stopped until those active jobs are completed (let's say they run until 10:10pm). At 10:05pm, another scheduled job was added to the queue. This schedule will now be marked as complete.
I agree. I've brought it up with Alteryx more than once. My workaround has been to include auto-kill functionality in my backup script to cancel actively running jobs. This effectively shortens the 'stopping' time of the AlteryxService, which reduces the likelihood of the 'completed' schedules bug. It's not ideal, but it works for us.