Default values not being included in if-else node

[samhbarton]

EDIT: The issue was the input contents were not actually present. I’ve noticed a number of times that sometimes when i add a default value or connect nodes and I press save, they are not applied so my run fails. When I look into the failed run, I see that the stuff that i thought was saved didn’t apply.

//

I’m testing out how to handle error reporting for a complex workflow that’s triggered via webhook.

I’m testing things out in a separate workbook using default values.

Problem: The If-else node with the default value condition is ‘not empty’, but when i run it it returns ‘FALSE.’ I would assume that the default value would be passed through here*

Workbook link: https://www.gumloop.com/pipeline?run_id=hqLWg6F4yicdNA6LgmkGHk&workbook_id=fViXtL78RLs1YxgaMbdztv

Thanks!

[Gumloop_Bot]

Hey @samhbarton! 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.

1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
   

3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

[Wasay-Gumloop]

Hey @samhbarton - By any chance was the default value added after or during runtime? On my end, I don’t see the default value:

This sort of setup should work though, here’s an example:

• True
• False

[Wasay-Gumloop]

@samhbarton read your edit. Just wanted to clarify a couple of things that might be relevant:

– In certain cases, the save can be “overridden”: for example, if you connect a node but don’t drag the input badge into one of the fields in the connected node, the connection lines will disappear on refresh or runtime. With the new UX update, a node can now accept multiple inputs, and to define a connection (i.e., what value the node receives), it’s necessary to drag the badge into one of the input fields. This might not be the exact case here, but worth mentioning.

– You also mentioned triggering this flow via webhook — just a heads-up that values populated from the webhook will replace the default value.

[samhbarton]

@Wasay-Gumloop thanks for the clarifications. It could definitely be happening due to me not dragging the badges over, but I think it still messes up sometimes.

I’ll keep an eye out and let you know if I see it happen again.

[Wasay-Gumloop]

Appreciate it, thank you! We’re also making improvements to the badge inputs like adding a slightly bigger surface area to drag & drop, if you have any suggestions feel free to drop them here.