Workflow failing because one step doesn't start

,


For whatever reason, the getHubspotContact doesn’t run…if I manually run it, it works fine, so it’s not an error. It just never starts. Is it somehow not getting the message to start because I have two things coming out of the trigger?

Note that the getHubspotContact node is definitely getting data if I check it out under executions.

Thanks,
JMR

Difficult to help if you don’t fill out your setup info

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
1 Like

Taking a guess you’re on v1+ and you’re using the new workflow execution order which is depth first.

In this case your update contact node runs from the first branch (and errors) before the get contact node can run.

You can either set continue on fail for the update contact node, or move the get contact node higher than uniqueCodes so it runs first.

1 Like

I’m on 1.05 and using all the default settings on the cloud set up and MacOS

OH…I see what you mean. Because that updateHubspotContact is situated higher up on the page, it’s run first before getHubspot contact. I wasn’t aware that’s the way it works! Thanks for clearing that up!

I would probably use a Merge here.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.