Solved! Go to Solution.
@Anonymous wrote:
Thanks for the speedy response, Brad! Just to verify, in order to use the Nested Flow with the Request and HTTP actions, I need to have Premium, correct?
Yes, HTTP requests require premium. With that said, you can do a "poor man's" version and run Flows on a schedule as an alternative. Example, Flow 1 runs at 12:00AM, and Flow 2 runs at 12:15AM. Not ideal, obviously but it can work in the right situations.
👨🏻💻 If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.
There is no way to clear the cache for your Flow, so you'd need to either name the split file a different name, or you could separate it into a second Nested Flow. So you'd be calling the second "read" Flow from the primary "write" Flow.
👨🏻💻 If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.
Thanks for the speedy response, Brad! Just to verify, in order to use the Nested Flow with the Request and HTTP actions, I need to have Premium, correct?
@Anonymous wrote:
Thanks for the speedy response, Brad! Just to verify, in order to use the Nested Flow with the Request and HTTP actions, I need to have Premium, correct?
Yes, HTTP requests require premium. With that said, you can do a "poor man's" version and run Flows on a schedule as an alternative. Example, Flow 1 runs at 12:00AM, and Flow 2 runs at 12:15AM. Not ideal, obviously but it can work in the right situations.
👨🏻💻 If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.
Thanks Brad!
All right, so I split my it into two separate flows:
1. The first flow receives the new file in an email, saves it, and sends a confirmation email.
2. The second flow has a manual trigger. It reads the file, splits it up into separate files, and emails the files.
Though the saving and reading steps are now in different flows, the List rows present in a table step is still using cached data. I thought this would mimic the Nested Flow, but maybe I'm missing a step? Is there another workaround you can think of?
Parent Flow: Save the new file in the specified location.
Child Flow: Read the file in the specified location.
User | Count |
---|---|
89 | |
41 | |
23 | |
20 | |
16 |
User | Count |
---|---|
130 | |
51 | |
48 | |
36 | |
26 |