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.
Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email firstname.lastname@example.org for assistance.
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!
Currently, failed job results stay in the Mongo DB forever. Please either make it adhere to the same coding in the Server Settings for "Delete queue and results after (days)" setting, or make it a separate option for failed jobs.
When a render tool is run on Designer pointed to a temporary file the log gives you a clickable link to access the output. When deployed to the Gallery unless you have given it a specific output destination with %temp% in the filename you get... nothing.
What did I expect? The pdf or other temp file to render on the screen or at least download for me. Or give me a dropdown selection of the various files render could create for me.
Issue: When Workflow names have similar beginnings on server a user cannot distinguish between them because the columns on this GUI are not expandable as would be expected. A user has to make their browser larger and all columns open proportionately.
Solution: Change column settings so users can drag column widths to make changes. A bonus would be to allow a user to set a default along with an option to always auto expand all.
We would like a built-in process that would search or, and resolve, workflows that are stuck in the "initializing" state. These seem to happen for various reasons but communication problems between the controller and workers .. usually a socket timeout.. which appears to be most problematic. It seems that these type of errors should be expected in all but the most stable environments,
Currently, the only tool that we have to solve this problem is to restart the Alteryx Service on the controller and while this works there tendency to cause some collateral damage in workflows ...erroring or restarting from their beginning.
There may be a way to solve this without restarting the service by editing Mongo using a tool like Robo 3T but that is unproven and has its own risk.
After dealing with this issue and struggling for quiet some time we think that the best option is to implement a "clean up" DB process that will run every 5 min or so, capture a list of workflows in the "initializing" state , then compare that list to one in the next 5 min cycle and fix any workflows that appear in both lists. We think that returning any stuck workflows to the queued state would be the best Fix option.
We just don't want to continue to use Restart the Service process to solve this issue and accept the collateral damage.
We have situations where some workflows that are scheduled end up having intermittent connection issues to other databases that result in the workflow running to timeout. The timeout settings are set in the server, but it would be nice if you could set an override value for a lesser timeout in the runtime settings for individual workflows and basically use the server setting as a not to exceed value. We have a multi-node environment with multiple worker nodes and about 250 artisans. We have some regularly scheduled workflows taking the full amount of time in the timeout setting and obviously if a couple of normally quick running workflows ran to timeout that causes issues with the queue.
I was recently hired by a fortune 500 company to eliminate use of their Access DB's by replacing them with Alteryx solutions. My first step is to understand the old DB's so I know what type of workflow to build. I'd love to have an ERD tool built in Alteryx to drop right after the input data tool. The closest I've found is the Network Analysis tool, but I don't see that giving me the desired output.
I would like to see how tables are connected, what manipulations are being done, when a query/view/macro was last used, what outputs being delivered.
I understand that the Timeout feature on all Workers is only available for the workflows scheduled on Alteryx Server.
In a heavily used server environment and depending on how workflows are configured, can we have a timeout feature available for non-scheduled workflows (adhoc workflow runs/manually triggered workflow runs) as well on all the Workers on Alteryx Server ?
I try to keep my studio up to date and remove unwanted or older versions of workflows. Yesterday, I inadvertently delete a workflow by mistake and it hadn't saved a copy on my laptop.
Talking to your tech team, to my horror I discovered that there is no 'Recycle bin' on Alteryx server. There were suggestions of how to recover it, all of which I was very grateful, but a lot of work to rectify a mistake.
My suggestion is for a recycle bin in scheduler so when a mistake is made, you have the ability to retrieve your work. It could have a time limit setting to automatically empty the bin after a set period or size, deleting the oldest files first?
I am an Artisan but not the Owner of the studio - I uploaded the workflow and would like to see all the jobs (including manually triggered) that run for my workflow so I can track any issues i.e. when workflow fails. I checked with the Owner of the studio and he also can see only the runs he triggered.
I understand from the Support team in my company that option to see all the jobs that run is currently available only for the Curator role but would be extremely helpful if you would make it available to all the users that have access to the Private Studio.
I would like to see ability to limit the number of versions a user can save of a workflow. As a server environment ages we start to see the database become unnecessarily larger because the number of version of workflows. For servers related to DEV and QA environments as an Admin I would like to be able to say users can keep their 10-25 most recent versions of their workflows. Then anything over that will start to auto-delete just like the auto save feature in Designer.