avoid infinite loop with 2 Workflows

(0) Share

Report

Posted on by RaulOcana

8,270

Hi guys,

I've created a WF that updates a text based on a lookup. But also a WF that updates the lookup based on a text. This is for a Marketo integration, so I must do it. This could be for any of my custom entities (Country, Industry, etc.).

Here the set up:

TextA is hidden field. It is only updated by a Marketo integration, or the 2nd WF.
LookupA is a Lead field that can be manually updated or by the 1st WF

WF is triggered by TextA. It reads TextA and updates LookupA.
WF is triggered by LookupA. It reads LookupA and updates TextA.

So when a user manually updates the LookupA on the Lead, it will trigger 2nd WF and update the TextA. But it will trigger 1st WF which then updates again (via WF this time) the LookupA.

Is there a way to AVOID this?

Maybe if the LookupA or the TextA already have the new value, it can ignores the update? Is there a way to compare OLD vs NEW value?

Thanks guys!

Regards,

Raúl

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (4)

Verified answer

ashlega 34,477 on at

Like (0)

Report

Is there a special user for Marketo integration? You might check "modified by" field in the workflows that's attached to TextA before doing anything (if "modified by" == "marketo integration user" then stop)

I'm guessing you might also create an extra field which would only be set from Marketo integration and configure the workflows that's attached to TextA to run on that field instead. In that case, when a lookup is updated, your lookup workflow won't be setting that special field, so the second workflow won't be starting

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Agree with Alex, You can check the integration user or use a field which you can set through JavaScript or business rule when the change is made via UI and check the same in the Workflow.

Was this reply helpful? Yes No
Verified answer

PS 23,577 on at

Like (0)

Report

Add a condition in both the workflows. This would be the first condition and then update.

In my case I have taken example of Lead Topic field and Opportunity Topic (renamed to objective in my crm) field. Originating lead is the lookup on opportunity:

Add: Originating Lead 'Topic' does not equal Opportunity 'Topic'

Was this reply helpful? Yes No
Verified answer

prt33k 6,907 on at

Like (0)

Report

You can handle it in two ways:

1) Put a check in data. If the data that you are going to update is already present then skip the update. This is similar to what Prashant suggested in above post.

2) Put a check on initiating user. So in you case the TextA gets updated my Marketo Integration which I believe runs under some service account. So when the modifying account is service account only then we Update the Lookup. And we update the Text on lookup change only when the initiating account is Not service account. This will require a custom workflow/plugin though.

Thanks,

PS

Was this reply helpful? Yes No
RaulOcana 8,270 on at

Like (0)

Report

Thanks guys.

I did all validations. Modified By and old vs new value!

Thanks!

Was this reply helpful? Yes No