Automation failed! Could not find next node

Get Help Pipeline Failure
1

My Flow is terminating prematurely (immediately following the execution of a Supabase Table Writer node) with the following error:

Automation Failed!
Could not find next node to run. Please double check the node connections.

No connections are missing between nodes. The flow splits into two branches. I originally thought one branch was terminating early and halting the entire flow before the second branch can finish; however, nothing I’ve tried seems to resolve the problem. Fixes I’ve tried without success include the following:

  1. Wrapping the Table Writer with an Error Shield
  2. Taking the nodes of one branch and making it a subflow of the other flow.
  3. Using a Custom Node at the head of the branch providing an either/or decision on which branch to execute.
  4. Numerous other routing and connection changes.

So far, nothing seems to work.

Has anyone encountered this before? Are there known causes (besides what’s implied by the error message) that I should be looking into?

Thanks in advance for the help!

https://www.gumloop.com/pipeline?workbook_id=pd9im912ok9SwzXL9voTNA&run_id=QJ94CvMaVWCsqCB2YMgWvY

2

Hey @Steve1! 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.
    GIF guide

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

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

3

Hey @Steve1 - Can you share access to the workbook please, instructions are listed in the message above :slight_smile:

4

done.
I also responded to the email from support with the workbook link.

5

Thank you @Steve1! This is definitely a confusing error. I made a quick video to explain this along with the fix: Google Chrome — Screen Studio

Let me know if this makes sense and works for you.

6

That makes sense. And the fix seems to be working well.

Thank you!

7

Awesome, glad to hear that!