The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

0 Likes

As you can see from the screen shot below, “Version 10” is my latest version, but I’ve selected “Version 9” to be the published version. When I hit “Run” or when I schedule a run, it is running version 10 instead of version 9. The only way for me to run version 9 is to click on it and select “Run Selected Version” (also in screen shot below).

 

This doesn’t seem logical to me that the runs are not using the published version. Would love to see this setting changed! :) 

 

Screen shot 1.pngScreen shot 2.png

 

0 Likes

Whilst executing long running jobs in Gallery, it would be useful to be able to view the log so I can judge progress.

0 Likes

A suggestion, in our environment, we see workflows getting into Initializing Status often in scheduler (this could be because of the environment we are in)

 

If workflow in “Initializing” Status > n minutes (where n is configurable)

  Then

Kill the workflow, and resubmit

 

Ref: Case # 00260492

0 Likes

Currently 'Schedules' are a separate category in the navigation bar on the left, and while it is nice to have an overview of all my workflows/apps, most of the time I need that information in the Private Studio screen where I'm checking in on the run status and getting ready to schedule the job again.

 

Additionally, Designer disables the schedule whenever it saves the workflow/app back to the Server. This is not always the desired intent when we make a small change to the workflow/app. Having an option to disable a current schedule would be better, with the default to keep the current schedule. Also, the abilty to manage the schedule from the Private Studio to say 'Activate' a disabled schedule, or schedule the workflow/app multiple times with different inputs would all be good.

0 Likes

A strange issue is found that the Alteryx Gallery schedule suddenly becomes disabled.  After checking with support, it looks like the mechanism underlying is using a concept of queueID.  Whenever there is a network issue between controller and worker, the queueID get scratched, the job gets corrupted.  This means it cannot calculate the next run and thus, it will disable the schedule.  When the worker node gets back, it cannot "try again".

 

From usage perspective, if network is having issue, it is assumed that the connection gets back, it would "re-try" and resume.

 

Hope Alteryx team can help consider a fix on this technical issue.

 

Thanks.

Top Liked Authors