Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
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

Alteryx Server Job Scheduling

Currently, Alteryx Server lacks rich job scheduling functionality to other products like Control-M and Informatica's Scheduler

 

Feature Requests:

 

1) Ability to configure job retries on failure without having to rerun the workflow based on a  event trigger: https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/How-to-run-a-workflow-from-an-event...

 

There are common occurrences where a workflow may fail to connect to Input sources and a retry would normally resolve the issue. 

 

2) More user friendly way to setup dependencies between scheduled workflows.  For example, if workflow A fails it triggers workflow B to run.  If workflow B runs without errors, it triggers workflow C to run.  Currently, we would need to configure this based upon events.  A complex chain of scheduled workflows becomes difficult to manage and scale.

 

3 Comments
jimfrb
5 - Atom

Forgot one important detail - CReW Alteryx Macros we find to be super valuable.  However, these macros lack Alteryx support.

CristonS
Alteryx Alumni (Retired)

hi @jimfrb, thank you for your ideas! We appreciate the time our users take to provide us feedback and help us improve our product. Be sure to check out our other product boards and user ideas as well as our updatedSubmission Guidelines

TomDiroff
Alteryx
Alteryx

I agree with the need for both of these,

 

In the case of #1 ... any connection that a workflow makes is subject to fail .. and that is especially true the farther the connection target is form the Workflow's server... why not have a retry option and provide the connection the opportunity to succeed on the next try? If the goal is to use workflows to create business value workflows should be made as robust as possible.

 

For #2 .. there are 3rd party solutions like Control-M and Autosys etc etc which may help but those are "YMMV" solutions.. Alteryx workflows again would be made more robust with a built in solution and as such better meet the goal of providing business value