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.
6/17/21: We have completed maintenance for the Search functionality on the Community. If you are seeing any issues, please try to clear your cache first. If the issue persists please email Community@alteryx.com
As a server admin, planned PM outages should be scheduled. These outages should prevent jobs from beginning execution (window of time) prior to the outage. Jobs running at the time of the cut-off should be system-cancelled.
As a server admin, unplanned outages should cause running jobs to stop. At the conclusion of an outage, jobs that are system cancelled should be restarted.
Currently, we use Task Manager to control Alteryx Service (or command line). An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities. While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't. Other admins have asked what is "hanging" alteryx service up for a STOP command. I have explained that all jobs must be stopped in order for a quick restart of the service.
We're using a single server today (this client) and plan to add workers to the configuration. It would be helpful to know where work is running and be able to use admin functions across the servers.