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.
I've seen various solutions/workarounds but this seems to be a table-stakes ask? When scheduling a workflow I should be able to specify which parameter values to run with. Just two of many use case examples -
Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business
Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials. When their credentials change all they would have to do is update the schedule parameters
(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)
I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.
Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1). However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)
Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.
I would like to set a retry count when scheduling a job, and also to specify to duration in between retries, e.g. job fails, but then will retry to run 3 times with a 5 minute wait in between each retry.
Also would like a radio button next to all workflow results, so when you get a list of failed jobs you can click all the jobs and then hit rerun. This should be complimented with select all functionality. This will prevent me from having to go into each job and rerunning, i.e. save me loadsa clicks!
It would be great if each user could persist their gallery UI sorting/view changes and leave them as default. When I log in I nearly always immediately switch to list view and sort by most recent modified. This means everytime I access a set of workflows there are at least 3 click actions before I can even start working.
I am leveraging the server as much as possible while working remote. I usually use it mostly for scheduled workflows when I am in the office, but limitations come up with the efficiency of the VPN and poor bandwidth when I am remote.
A typical process is to save to server, validation cycle runs, then open the workflow on the server in a browser, click run.
An ideal would be a macro or option that would combine two steps; for example, instead of "Save to Server", "Save to Server and RUN". At that point you can collect your workflow when it is down running.
As part of the Persistence Expiration processes, within Designer we have the ability to set a retention threshold of the results tab. i.e. 30 days.
After enabling this - all completed results are purged but all the "error" results remain. And this depending on the original count can run into the thousands, such as in my environment. Id like to see the "Error" results become part of the clean up processing because of the following reasons:
1. We do not have dedicated admins that have time to manually or by group delete these error result items.
2. Most if not all - errors are resolved immediately. if there were to be kept as a reference, a screen shot of the results are normally taken and filed away.
Support says this is intentional for resolution tracking purposes - but to counter - as I stated in item 2 - most errors are immediately looked at and worked on. So there is no reason to keep errored results. Especially when they are time-stamped dates greater than the expiration values selected.