Hey @michaelraspuzzi! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @michaelraspuzzi – Yes, exactly. A `Join Paths node would work perfectly here. Its purpose is to merge outputs from any given node, whether it’s the success or error branch, or any mutually exclusive branches.
For example, the join paths node can take both the success and error outputs of a node and continue down to the combined text node, even if inputs are empty.
I’ve set that up in the workflow below. Feel free to make a copy and test it out. Let me know if that works.