I want my Interface to handle either textor a urlor a file upload on any given run.
However, with two of the three parallel processing flows handling blank outputs on a run, my runs kept getting errors. Some of the nodes couldn’t handle blank outputs/inputs.
I can’t figure out how to route my blank outputs through the flow in a way that won’t stop the flow AND accounts for the fact that on any flow, any two of the three fields would be firing blanks.
Does anyone know best practices for handling blank outputs in a flow?
I’m still relatively new at Gumloop and automation and the If/Else and Filter nodes are breaking my brain.
And at the end of the day, I don’t know which nodes can “nullify” a blank output to keep the rest of the flow going.
Hey @will.sturgeon! 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 @will.sturgeon – I think you’re super close. There are a few ways to set this up, but the most robust option is using the Join Paths node. Here’s an example: Gumloop Pipeline
You can check out a walkthrough of the workflow here: Loom Explanation
Let me know if this makes sense and works for you.
Thank you SO much for the tutorial video. It really helped cement my understanding of how Join Paths + Error Shield nodes work together (I promised I watched the tutorials—I just couldn’t crack it and didn’t get that straight of an answer in the online tutorials I watched)
Your customer service—sending 6m tutorial video within 2 hrs of the question—is crazy and makes me already way more a fan of Gumloop than I already am. Thank you @Wasay-Gumloop!
Unfortunately, I’m coming up with another unknown error on this flow. When I run it in the Workbook, it completes!
But running it through the Interface brings me some problems.
When running a flow from the Interface, I get an error message. When I run the same inputs but in the Workbook, the flow completes.
Also, sometimes running it through the Interface just straight up has disconnected paths from the Interface nodes to the next nodes in my Workbook for some unknown reason, but I don’t have an example of that to show you.
Why would I be getting different outcomes when adding inputs via the Interface stand-alone page vs. adding inputs via the Interface form in the Workbook?
Hey! The replace() argument 2 must be str, not None seems to be a bug on our end. Created an urgent ticket for this to look at it on Monday, will keep you posted. Sorry about the hassle.
Also, sometimes running it through the Interface just straight up has disconnected paths from the Interface nodes to the next nodes in my Workbook for some unknown reason, but I don’t have an example of that to show you.
That’s likely because no input badge was added to the connected node. Without a badge, it’s treated as having no connection. We decided to remove those lines to avoid confusion when badges aren’t present.
