ERROR: The property couldn't be set because the contact isn't associated with any target records.

[LCarroll00]

I have a workflow that initally worked as expected, but started failing after the initial run of contacts went through. In summary, after a contact completes another workflow that creates a deal it is to be enrolled in my workflow to assign a propety value to the associated deal.

Unfortunatley I am getting this error message above whenever a contact moves through, even though I know for 100% certainty that a deal is created for that contact. I went back through and re-enrolled contacts and am still getting the same error message, again I know that they have deals associated with them.

Why did the workflow work with the original run or contacts, and why did it start failing after that?

Here is a screenshot of the enrollment trigger: 

[karstenkoehler]

Hi @LCarroll00,

Can you please share screenshots of both workflows and the enrollment criteria of both workflows?

Things like these are typically due to a race condition. While it seems like one workflow would run before the other, things are simply happening too fast for HubSpot to register them in the correct order. The moment HubSpot is supposed to evaluate something for a enrollment, a branch, a workflow action, whatever is supposed to be completed by that time simply isn't.

If you share the aforementioned screenshots, I can elaborate.

Best regards

[LCarroll00]

I thought that was maybe the case, but I re-enrolled everyone who had been previously enrolled, knowing there were a number of errors, and they still did not update.  Here is  a snippet of the broken workflow: 

The branch is checking for this for all users: 

It would make sense to me that without including a delay, this workflow would fail under normal conditions, but I do not understand how it failed on the re-enrollment.

[karstenkoehler]

@LCarroll00 can you please share screenshots of both workflows? It's not possible to troubleshoot this just seeing a piece of the process.

[LCarroll00]

Here are images of both workflows. The first image is of the first workflow in the sequence - it works as expected. 

The second image is for the broken workflow: 

 

[karstenkoehler · Accepted solution]

@LCarroll00 thank you – I just noticed that the second workflow enrolls records based on enrollment in the first, not completion of the first. In other words, they fire at the exact same time.

Secondly, can you confirm that the "Create record" workflow action actually establishes an assocation between the records?

[LCarroll00]

Yes, I noticed that they are firing at the same time too! I just added a one-hour delay to that workflow, which should solve the problem there. 

Regarding your second question, I can confirm that the contact is being associated to the deal.

[karstenkoehler]

@LCarroll00 have you looked up the action logs for records where you are sure a deal is created and associated correctly? https://knowledge.hubspot.com/workflows/understand-your-workflow-details-page

[JWingate2]

Hi @LCarroll00 , 

The issue could be that Workflow B is just looking to see that they were enrolled in Workflow A (Fitcall led to S1), so they are enrolled simultaneously. Changing the enrollment to "Has Completed" workflow A (Fitcall led to S1) might be better.