https://www.gumloop.com/pipeline?workbook_id=pdnPcpJfYVQ7hsUpsa22KN&run_id=bgACMxFswMwCf7ZM3qCvVb
Hey @Luv_Goel! 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.
You can find your run history here: https://www.gumloop.com/history
Hey @Luv_Goel – It seems like the input was not connected properly. With the new update you need to specify what the node receives as input using the badges.
Let me know if this makes sense and works for you
Hey, Yes this new approach is working now. Thanks for the response.
I have a feedback on this new work around. The dragging of the inputs into the node is not an intuitive thing to do, if one does not know this, for the first time users. Atleast, when there is just one connection, this should prepopulate the single input directly. And for multiple connections, the inputs to drag should be a little bigger in size as compared to the scale of the workflow, to make it easier for people using it first time to realize that inputs are filled up using drag and drop.
Thanks
Really appreciate the feedback and something that we’re already considering, much more improvements to come
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.