Chained Gallery app Concurrent Users Conundrum

We are running into an issue with a chained app in the Gallery that passes data through the chain.

As each app in the chain creates a separate temp file, we are using a network drive so save the files from app#1 that are picked up in app#2 or app#3 etc.

The issue comes in with concurrent users. Depending on selections made, User#2's project may complete before User#1's project causing User#1's data to be overwritten and hence providing incorrect results.

Is there a way pass the information from app#1 to app#2 without writing to a temp file on a network drive, or to identify the temp folder used by app#1 in subsequent apps in the chain?

Thank you.

Gallery

Dynamic Processing

Chained App

Accepted answers

MarqueeCrew

Robb,

I'd likely suggest something like: Use a GUID to create a subdirectory where subsequent jobs look into a private set of data rather than into the general temp pool.

A short and directional answer....

See you at inspire!

Mark

All comments

MarqueeCrew

Robb,

I'd likely suggest something like: Use a GUID to create a subdirectory where subsequent jobs look into a private set of data rather than into the general temp pool.

A short and directional answer....

See you at inspire!

Mark

KMiller

Hi @MarqueeCrew

I have this same problem. I have taken a GUID type approach, using the __CloudUserId script to identify the user and create output files from workflow 1 with the users Server id. However I am having trouble figuring out how to get workflow 2 to dynamically select the users input files for a drop down or list box, using an external source. Do you know of a way to update the below file path dynamically in the workflow.

Thanks.

Kevin

hroderick-thr

I'd like to add a plug for my new idea,https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Chained-App-User-Variables/idi-p/783758

This would be much simpler than other approaches explained here.

I'm not certain all workflows in a chain would run on the same worker server, blowing the relative file directory solution.

Also, I like having the passed data available on a shared drive so I can audit, test, and debug easier

Right now I'm getting __cloudUserid in every workflow in the chain to build into workspace directory names.

I wish we could get the __cloudUserid only in the first app of a chain, and add a timestamp to it, giving a unique meaningful subdirectory name that could pass to the next step in the chain..so I posted the idea and hoping for the best.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703