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.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
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!
A user approached me today with a problem of "Many people need access to the results of this data, and I want everyone to be able to see all the results". While you could potentially email these results to a specified user set, that would require maintaining both a collection and an email tool in the job, and could potentially cause notification fatigue if users only care when they go to the Alteryx Gallery. Similarly, results could be saved to a networked location, but that would require a user to go to two locations in order to find this information.
As such, having a toggle that allows users with permission to view a workflow, to also see the results of any/all users, would be huge.
We use external corporate scheduler and we would like to start scheduling Alteryx workflows in this way. However, collections don't have API which would simplify our way of running workflows which we are shared by the users. Are you planning to enable such feature?
For professional alteryx admins - it is important to know if a particular asset has been updated (so that we can bring the updated version into our env), with some idea of release notes so that we can understand if the update breaks backward compatibiity and what has been changed.
Additionally - it would be very helpful for admins to be able to be notified of new assets created by particular authors whom I trust.
I have tables that I need to run ETL jobs on every 5 mins. But, a batch job runs every day for an hour at the same hour. During that time I can't query the source. With the current scheduler setup; it appears that my only option would be set up multiple schedules. Each running once a day, and a separate schedule for every 5 minute increment of the day with the exception of the one hour my source can't be touched. Rather than that degree of hassle, doesn't it make more sense to set up a scheduled with and/or/not criteria? Example: Run every X minutes on Y days Except: during %t am - %t am on Z days
I've seen some applications that have a visual scheduler for setting the exception times. That would be pretty cool too. Bonus points if you can make an admin console for the server which allows the admin to set blackout date/time by table or DSN for all users (override their schedules).
We have several workflows that call other workflows (i.e. via the Conditional Runner macro) but are running into some versioning challenges since we moved to storing all of our workflows in our gallery. When I publish a workflow that references another workflow, I can bundle it up with the workflow when I save it, but then Alteryx places that workflow into the /externals directory, which is obvioulsy not the same as the workflow that we've saved to our gallery. An example:
I have two workflows in our gallery...one that generates a TDE and one that calls that one if certain file availability and time conditions are met. The "master" version of each is in the gallery, which is what we want...
...but when I load or save the Sales Analytics workflow in Designer, I have to bundle the TDE workflow with the main workflow in order for it to run from Gallery. But now I've created a disconnected version of the TDE workflow and if I forget to update it when I update the version in the Gallery, I'll be running the wrong version. I know I could store these workflows in a network directory, but that seems to defeat the purpose of the Gallery.
If I'm not missing something insanely obvious, I think this would be a very important feature enhancement, namely the ability to pull in a Gallery workflow into another workflow.