Welcome to the Alteryx Knowledge Base

Note: As of version 22.1, Server does not wait for workflows to finish, it cancels them. It is a work on progress issue.

For a setup that is configured to run on multiple nodes/servers, please review the recommended order to stop and start the services during server maintenance or upgrades.
 

 Procedure

Shutdown:

1. Workers
   1. If stopped, the service on the Worker machine will shut down gracefully if allowed once all workflows have completed or been cancelled. It is not recommended to stop the service on a worker forcefully as output data or database writes could be impacted.
   2. Can be interchanged with Gallery, if you wish users to not be able to queue additional jobs through the Gallery while workers are shutting down
2. Gallery
   1. Can be interchanged with Workers, may result in longer downtime of the Gallery
3. Controller
4. MongoDB (Optional)
   1. Only necessary during upgrades or if required for other operations

Startup:

1. MongoDB (Optional)
   1. Only necessary if the database was shut down previously
2. Controller
3. Gallery / Worker(s)
   1. No specific order is necessary, but you may consider bringing up Workers first to avoid extra queued jobs coming from Gallery users

Reasoning behind the order:

• The reasoning for the shutdown order is so that your Gallery is down the least amount of time - but you may wish to change that order if you don't want users submitting more jobs to Gallery > Workers.
• But if this is done, then your Gallery outage could be much longer depending on jobs completing/cancelling.
• Users can queue new jobs while workers are down but they won't run - which is the downside of leaving the Gallery up, but they can also still look at previous job results and current job execution via Gallery until it's completed.