Problem with cloning deal through workflow - infinite loop

[Szymon_Rogozik]

Hi,

I am trying to create a clone deal using a workflow. I read that I can do this using workflow, but when I do it i get the message “The enrolled deal was created by this workflow, so this action was skipped to prevent an infinite loop. ”

The workflow is supposed to work in such a way that if a deal fails, it remains in the failure stage, but a copy is created and moved to another transaction stage in the same pipeline (essential properties are cloned, contact and company are removed)

Is it possible to perform such a process?

[Szymon_Rogozik]

I will describe what I mean.

Original deal - I act with customer X, but eventually the deal fails. The deal goes to the FAIL stage. The "Oryginal deal (1)" remains associated with customer X.

Workflow creates a copy of the “Original deal” and inserts it at the beginning of the pipeline retaining all properties but it is not associated with any customer.

Cloned deal (1) - I associate it with customer Y and act with the customer. Eventually the deal fails, and goes to the FAIL stage. “Cloned deal (1) remains associated with customer Y.

Worflow creates another copy of the “Cloned deal (1)” and puts it back to the beginning of the pipeline retaining all properties, but it is not associated with any customer.

Cloned deal (2) - I associate it with customer Z and act with the customer.

This repeats until the deal is closed WON. 

Basically, the idea is that there is a pool of 100 deals that are very specifically parameterized. The customer doesn't want to create new deals, he wants to use specifically the 100 already parameterized ones. At the same time, keeping information about how many times a particular deal (original and cloned) was at the failure stage.

Deal represents an apartment in the building

[karstenkoehler]

@Szymon_Rogozik are you seeing a conflict with my last reply? This would not require reenrollment as each deal only passes through the workflow once. If the closed lost stage triggers the workflow and the new deal is placed at the beginning of the pipeline, there shouldn't be any issues.

[Szymon_Rogozik]

It seems that to disable the re-enrollment criterion should take care of the issue, but something is not working for me.

Moving a cloned deal (Cloned deal (1)) to the end of the pipeline does not create a new deal (Cloned deal (2)).

Instead, it gets the message that “The enrolled deal was created by this workflow, so this action was skipped to prevent an infinite loop.”

It seems as if the system recognizes that the clone was created by the system and does not allow it to be cloned again....

[karstenkoehler · Accepted solution]

@Szymon_Rogozik you should be able to work around this with two workflows that are identical to except for two aspects:

• Workflow one sets a custom property value on the newly created deal to the value A
• Workflow two only enrolls deals with value A
• Workflow two sets the value on the newly created record to B
• Workflow one only enrolls records with value B

Still a loop but last I tested, HubSpot didn't notice.

[Szymon_Rogozik]

Brilliant! It works 🙂

[Szymon_Rogozik]

Thanks for the answer.

I turned off “Allow deals to re-enroll after completing the workflow” and this partially solved the problem. The original deal moved to the “Failure” stage is cloned and moved to the appropriate stage.

The question is whether there is a way to make this cycle repeatable? I mean, when the deal created by the workflow (clone) again hits the “Failure” stage it will again clone itself and revert to the appropriate stage?

I would like it to be possible to reproduce such a cycle several times.

 

 

  

[karstenkoehler]

@Szymon_Rogozik I am not sure whether I can follow - do you want the original deal to reenroll or the cloned deal to enroll when it meets the criteria? If it's the latter, no reenrollment would be needed - it's not the originally nap deal enrolling for the second time but the new one for the first time.

[Szymon_Rogozik]

I will describe what I mean.

Original deal - I act with customer X, but eventually the deal fails. The deal goes to the FAIL stage. The "Oryginal deal (1)" remains associated with customer X.

Workflow creates a copy of the “Original deal” and inserts it at the beginning of the pipeline retaining all properties but it is not associated with any customer.

Cloned deal (1) - I associate it with customer Y and act with the customer. Eventually the deal fails, and goes to the FAIL stage. “Cloned deal (1) remains associated with customer Y.

Worflow creates another copy of the “Cloned deal (1)” and puts it back to the beginning of the pipeline retaining all properties, but it is not associated with any customer.

Cloned deal (2) - I associate it with customer Z and act with the customer.

This repeats until the deal is closed WON. 

Basically, the idea is that there is a pool of 100 deals that are very specifically parameterized. The customer doesn't want to create new deals, he wants to use specifically the 100 already parameterized ones. At the same time, keeping information about how many times a particular deal (original and cloned) was at the failure stage.

Deal represents an apartment in the building

[karstenkoehler]

Hi @Szymon_Rogozik,

Could you please share a screenshot of your workflow (including all actions), a screenshot of the detailed enrollment criteria and re-enrollment settings? Without seeing those, it's hard to say which adjustments exactly would have to be made.

It does however sound like you would simply have to adjust the enrollment criteria in a way that deals created by this workflow do not qualify for enrollment, e.g. by passing on a value that they were created automatically, by setting a date stamp or similar – then excluding records with this flag from enrolling.

Whether you have set up branches for contingencies within the workflow doesn't matter. HubSpot must stop the loop directly at the enrollment step.

Best regards