Hey @Steven! 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.
I just resumed the flow on my end and created a new CSV, here’s the file (access provided to your account only) and here’s the full run link. I also topped up your account so you can continue building.
I’d recommend looking into a subflow approach (ie merging AI Web Research + Google Sheet Writer in a subflow) that way all data is added to a spreadsheet as soon as it is processed. You can also wrap the subflow in an error shield to prevent any one off errors from halting the flow. Subflow Tutorial Here.
Oh, got it- sorry, I didn’t scroll through the log itself to see the full error message.
I appreciate you running the workflow through completion and sharing the file! And thank you as well for sharing the additional info on the subflow build. What do you mean by topping up my account?
The reason why the CSV writer node could not be executed is because the output name on the AI Web Research node changed from Aum to Assets Under Management likely because the prompt was re-generated.