Surfing the onion - nested Flows & Tasks in Architect

I'm building out an Inbound Call Flow with Salesforce Data Actions, and I'm trying to use nested flows/tasks to collect data from the caller & submit it to Salesforce. I have a web service that allows me to submit log records to Salesforce using Call Data Actions to help me locate the call within the various flows it traverses.

We have a Dev. inbound call flow (1) with a transfer to flow (flow #2); call it 'Logger.' Logger creates a record with the Call.Ani, then transfers to flow (#3) with additional Call Data Actions to identify the Contact/caller in Salesforce, log that information, and finally transfer to flow (#4) that collects caller inputs, writes data to Salesforce, and responds with the results.

I've been adding new Call Data Actions within the various flows, and including the flow name and Flow.Version, and while the innermost flow is working correctly otherwise, I'm not seeing logs from there.

Do I need to save/publish each flow in turn, from innermost to outermost, to ensure that IVR is running the latest updates, i.e. make a change at level #4, save/publish, then save/publish #3, #2, and #1 in order? Do I need to replace the [Transfer to Flow] node each time the referenced Flow is changed?

You need to publish a flow to make the changes live. The order in which you publish the flows doesn't matter; when a call is made it will hit the current published version of each flow it traverses. You do not need to modify the Transfer to Flow action.

They are all published, as later versions of their respective flows (and not 'saved as' versions that might not be referenced). Hmm... it doesn't look too bad if I remove that innermost flow (#4), republish #3, validate w/ a call or two, then add #4 back in. I'll let you know...

I did find a bad filter on my side, so I am now seeing some of the innermost logs; could be some of them aren't writing to Salesforce for some as-yet-unknown reason, but it's closer. Someone suggested I capture a unique call attribute so that these logs can be reported on (not that I intend to keep them around long) to help troubleshoot -- sigh .. I guess I'll do that, now ..

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.