A customer is experiencing an issue with duplicate participants being created, and the auto-remove participant functionality is not working all of the time.

Why are there duplicate participants being created in my org?

VIKRAM:

There is an issue with one of the workflow rules written, which was firing the Advologix trigger in a recursive way. The customer is converting that workflow rule to a process builder to avoid this. But from the product improvement point of view, I would add this as something to improve in the Advologix Matter trigger, which is creating a participant. That trigger needs to be checked for the recursive call to avoid this in the future for any other customer.

VARUN:

Let's add this to a Knowledge Article so that next time this comes up, we also verify in user org - if there is a Process builder that is executing in recursion, i.e., calling again and again on field updates.

Our initial internal investigation did not find issues with a Workflow executing a field update causing duplicate issues. So it points me to the fact that Workflow Rule also needs to be executing a specific kind of field update only to cause this issue.

Also, there are ways this can be resolved without having our application changed:

• Make workflow rule only evaluate or update if certain conditions (field values) are updated to satisfy the condition.
• Use Process Builder with a similar condition check.

Workflow Rules, with field updates, fire one-time apex triggers again. I think we can live with this, it isn't that kind of road blocking issue to me that needs any immediate attention.

We can keep an eye on this. If it is replicated in other organizations in the same way, I may consider doing something about it. Or if someone vetoes me here and wants this fixed, then let me know.