Using cached input on downstream chained apps

[mike_r_johnston]

Hello. I currently have a workflow that audits several tables and files of HR data. The original workflow started small but out of necessity has grown to take a large amount of time and resources to run all the checks and processes required. I recently started breaking various steps out into individual workflows with the intention to create a set of chained apps and to run them as standalone modules for running individual processes. However, I cannot find a way to ensure that data cached on the first app can be reused or recalled as an input on downstream apps. Is that possible?

[OTrieger]

@mike_r_johnston 
Have you tried to create an output of one app that will be the input of the next app? 

[mike_r_johnston]

Thanks for the response! I considered it, but for most of the inputs there are no changes being made, so it would make just as much sense to use the same input again without caching. Two of them are large enough that the caching takes a couple of minutes, and the goal was to avoid repeating the time spent doing that. There is one input that will be edited and I save it as an output to use as an input on the next app.

[OTrieger]

If the starting point is similar for the different part of the automation, what you can try will be instead of splitting it to different app. do macros, take one part that you wanted to separate as a new app. and turn it into a macro. /and in that way you will have let say 8 macros in one automation instead of one big missive automation. In that scenario will need need to upload the input data only one time.