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.
Add Admin ability to place the Alteryx Service (Engine) into Maintenance mode allowing current workflows to complete, but all new workflow processing moved into Queue to allow for server configuration and/or maintenance.
Currently, if I want to make a small configuration change (like a memory setting in the Runtime settings) I have to hunt for a quiet window or the lowest level of activity to kill the service (and the running jobs).
It would be helpful to flip a 'switch' and have all new jobs go into 'Queue' allowing for the change and service stop/restart ... then pick right back up with the queue in configured order. (execution time, priority level, etc...)
When a user publishes and schedules a workflow on the gallery, they have the option to specify their time zone to ensure that the execution of the workflow occurs at the appropriate time. However, if the workflow invokes the DateTimeNow() function, the captured time is in UTC. If it is important for the end-user to have that time that is captured be in their local time zone, they will need to manually (either within the workflow or as a user input for an Analytic App) specify the offset from UTC.
Instead, there should be an Engine variable that captures the offset (or the time zone) that the workflow was executed from (or scheduled in), which can dynamically adjust the DateTimeNow() output appropriately.
Allow admins to configure an outage window(s) of a specified amount of time (say 5-6pm every sunday) for conducting admin activities. Specifically this outage window would block any scheduled jobs, drive any manual started jobs to queue, and also issue a popup on the gallery to notify users that it's during an outage window.
When using In-DB with iSeries over Generic ODBC everything works fine in Designer however when executing via Gallery process fails because a semi-colon ";" is added to the SQL statement as a terminator character and iSeries rejects this SQL0104 - Token ; was not valid. Valid Values < END OF STATEMENT >