Alteryx Server Ideas

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. 

Hello,

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. 

Thanks!

Gina

Good Day.

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.

Thank you for your consideration

Tom D  

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.

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.

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.