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.
After upgrading Alteryx Server successfully all Scheduled Workflows are in the state of "Queued".
The below error is present in the Service Logs:
Default location: C:\ProgramData\Alteryx\Service.
Error Message : "There was an error in Slave_Thread::DoWork: Server Error: 500 Server Error Key fields must be a WString: AS_Schedules__ID”.
The Scheduled Workflows show as queued with no jobs running in both "View Schedules" and Gallery.
A good first step would be to confirm that these options have been checked:
Scheduled jobs are in a state of Queued.
The above errors are present in the logs.
Alteryx Service is running.
Users can log in to Gallery.
Users can see their Studios and Workflows.
"Run unassigned jobs" is checked in Alteryx System Settings > Worker > General
Worker > General "Allow machine to run scheduled Alteryx workflows" is checked.
This can occur if server was upgraded when not all jobs had completed successfully.
1. Open Alteryx Designer on the Alteryx Server machine. 2. Go to View Schedules and connect to the controller if not already connected.
3. Switch to the Queue tab and start by selecting the oldest queued job in the list
4. Cancel them and continue to cancel until they start running or the queue is empty
5. This should free up the queue of any blocks and the schedules jobs should start running on their own. 6. If this does not help you clear the queue contact support by emailing email@example.com with the below information:
RuntimeSettings.xml (from %programdata%/Alteryx) from all nodes if multi-node setup