[Impacting all my flows] Input nodes gets auto detached with no notification of error

[guptasarthak10]

Hey

Loom: Troubleshooting Automation Errors 🤔 | Loom
Pipeline: https://www.gumloop.com/pipeline?run_id=7ZbDLHS3y2LqFQFZwwn57H&workbook_id=bSzfjRYoqNJTZnbx6cYabf&tab=3

[Gumloop_Bot]

Hey @guptasarthak10! 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 @guptasarthak10, thanks for flagging this!

This can happen if the interface input names were changed, the subflow input names were updated, or the subflow was duplicated. Once you fix and remap the badges, they should remain intact and won’t revert to node IDs at runtime.

We’re working on handling these edge cases so badges always stay intact—but apart from these, have you found any other ways to reproduce this?

Also, could you share access by either adding my email or setting the workbook to “anyone with the link can view” from the Share button on the run link.

Sent you some credits to make up for the trouble!