# Force re-enrollment on property changes

**URL:** <https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095>\
**Category:** Lists, Lead Scoring & Workflows\
**Created:** [April 16, 2020, 7:07am UTC](https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095 "2020-04-16T07:07:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![KPA](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kpa/32/29368_2.png) [@KPA](https://community.hubspot.com/u/KPA)\
**Post date:** [April 16, 2020, 7:07am UTC](https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095/1 "2020-04-16T07:07:20Z")

</div>

We have a custom property _A_ that we’d like to be computed based on a few other properties: _B, C_ and _D_.

So we’ve created a workflow that has _B, C_ and _D_ in enrollment and re-enrollment triggers and implemented an if/then logic to set the correct value for _A_ depending on _B, C_ and _D_ values\*.\*

When one of the properties _B, C_ or _D_ changes the contact is re-enrolled and _A_ is updated.

In general this works fine, but a problem happens when a few concurrent changes are made.

Ex.: _B_ is changed, so contact meets the re-enrollment criteria and workflow is started. When the workflow is running user updates _C_, so it must affect the value of _A_, but this change is ignored because of this limitation: “An object won’t re-enroll in a workflow while it’s already enrolled”. As a result _A_ has a value based on a new value of _B_ and an old value of _C._

If I manually re-enroll this contact _A_ is fixed, but how can I do this automatically?

---

<div class="post-metadata">

**Author:** ![Bruno\_Teixeira](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bruno_teixeira/32/19215_2.png) [@Bruno\_Teixeira](https://community.hubspot.com/u/Bruno_Teixeira)\
**Post date:** [April 17, 2020, 11:16am UTC](https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095/2 "2020-04-17T11:16:48Z")

</div>

Hello, did you add B, C and D as Enrollment trigger like :

B is known

or

C is known

or

D is known

For having them re-enrolling automatically everytime, you should do like this and of course on the re-enrollment tab, you should tick the box for them.

---

<div class="post-metadata">

**Author:** ![KPA](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kpa/32/29368_2.png) [@KPA](https://community.hubspot.com/u/KPA)\
**Post date:** [April 17, 2020, 12:33pm UTC](https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095/3 "2020-04-17T12:33:12Z")

</div>

Hello Bruno, thanks for response.

> * * *
> 
> [@Bruno\_Teixeira](https://community.hubspot.com/t5/user/viewprofilepage/user-id/84940) wrote:
> 
> Hello, did you add B, C and D as Enrollment trigger like :
> 
> B is known
> 
> or
> 
> C is known
> 
> or
> 
> D is known
> 
> * * *

Exactly, so usually a contact is retriggered once B or C or D is changed.

But not if these properties are changed too quickly.

The most trivial example would look like this:

 ![Annotation 2020-04-17 150315.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/2/c2b045720b1eb031fba19b80c289966dd9ac97e8.jpeg)

So if I change “Login frequency” to 10 the re-enrollment is triggered.

Then I quickly change “Login frequency” back to 1 while this workflow is in progress.

When the workflow is finished “Is engaged user” will be “Yes” even though “Login frequency” is already set back to 1.

Here are the logs from a real-world example:

 ![Annotation 2020-04-17 152546.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/6/8/6867d66545c1eacf766a6e719997d5eaa0110be8.jpeg)

As far as I understand this happens because of “An object won’t re-enroll in a workflow while it’s already enrolled”([Add re-enrollment triggers to a workflow](https://knowledge.hubspot.com/workflows/add-re-enrollment-triggers-to-a-workflow)). But I don’t know if it’s possible to overcome this limitation. Any suggestions?

PS. We’ve encountered this issue a few times while testing the workflow on test portal. So maybe it’ll work well on prod.

---

<div class="post-metadata">

**Author:** ![MikeCormack](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mikecormack/32/22307_2.png) [@MikeCormack](https://community.hubspot.com/u/MikeCormack)\
**Post date:** [April 20, 2020, 12:51pm UTC](https://community.hubspot.com/t/force-re-enrollment-on-property-changes/20095/4 "2020-04-20T12:51:46Z")

</div>

That’s right you have to use a workflow goals to remove the from the active workflow and Another one probably with a delay to then re-add them at the top, having been removed, probably doing this with a custom property for the goal that you can reset so they are not triggering it on reentry.
