Hi,
I looked across the community but didn't find any answer to this question :
How can I run a chained workflow from first to last step using the API ?
When I get the workflow information I get :
{
...
isChained: true,
...
}
Then, I can run the first step using POST on /v1/workflows/{appId}/jobs/ and obtain a job with its id and outputs.
But now I'm stuck, how can I run the next step ?
Please let me know if there is any missing information.
Regards.
Solved! Go to Solution.
Hi @NPatryC4
Thank you for your query.
Have you reviewed the following article that highlights the different options for chaining workflows together ?
There are different options depending on whether you will only use Alteryx Designer or if you will use Designer with Scheduler.
Thanks,
Conor
Hi Conor,
Yeah, I saw this post, and we have some chained workflows using the last presented technique, using the Interface tool. They run fine when we run them through our gallery.
My question was more technical, I want to run those workflows using the API. At the moment I just managed to run the very first part of those workflows ; "simple" (not chained) workflows run fine too.
Thanks.
Hi @NPatryC4
Thanks for providing more clarity.
Can you email support@alteryx.com where a Customer Support case will be opened for this query.
Can you also please attach the chained workflows to your email and a CSE will be able to advise further ?
Thanks,
Conor
If anyone comes here for the same issue, I contacted the support and there is currently no plan on implementing this, and no workaround except manually chaining workflows together (ie. create n workflows instead of 1 workflow containing n steps).
I created an Idea post here.
have developed a GalleryRunner macro which will run as chained apps . If interested let me know .
Yes I will tomorrow.
Hi NPatryC4:
If I am understanding correctly, your use case may be very similar to mine. I wanted to run a workflow through the API and determine if it completed successfully before running he next workflow. I was able to accomplish this by building two macros (okay, two macros that rely on other macros).
Using these in tandem enabled me to do what you described without the need for chaining apps.