I have a workflow where at reaching certain score a workflow will trigger and move a contact from lead to MQL
Now, there are certain parameters in scoring where there is substraction n addition. I am facing an issue at the moment the score is being calculated so at that time my score reaches a trigger score it gets enroll but since score is still being calculated the substraction parameters lowers the score below the threshold but the workflow has already moved contacts to MQL stage.
What I want with this workflow is that it should allow the score to settle or stable in this case
Has anyone faced similar issue. Is there a workaround for this
Hi @PMenkar1,
If the score “movements” are too fast and subtractions are too slow, in your workflow, simply add a 5 minute delay after enrollment (or 10 or 15), then set the lifecycle stage.
In the enrollment criteria, make sure to select the option to unenroll contacts if they do not meet the enrollment criteria anymore.
That way, if the score goes below the threshold within those 5 minutes, they’ll simply be unenrolled before they are marked as MQL.
Best regards
@karstenkoehler thank you this should help, I have a followup ask regarding renenrolment
How do I enable renrolment for this coz renenrolment is not possible for scores parameters
@PMenkar1 works for me 
I see what you did there
Thanks again
Hey @PMenkar1 !
Yes, this is a really common issue, and the best part is that the fix is actually pretty simple.
So, what’s happening is that HubSpot enrolls the contact the moment the score crosses your threshold, but your scoring model hasn’t finished calculating yet. The subtractions process a few seconds later, which drops the score back below the threshold, but the contact is already enrolled and moved to MQL.
What you can simply do is add a short delay before the lifecycle stage change
Just add a 5, 10, or 15 minute delay after enrollment, then set the lifecycle stage to MQL after that delay. This gives the score time to fully settle before any action is taken.
Now, this is the important part: in your enrollment criteria, turn on the option to unenroll contacts if they no longer meet the criteria. That way, if the score drops below the threshold during the delay, the contact gets unenrolled before they’re ever marked as MQL. Your workflow should look like this:
- Enrollment trigger: Score reaches threshold
- Step 1: Delay (5-15 minutes)
- Step 2: If/Then branch - is score still above threshold?
- Yes: Set lifecycle to MQL
- No: End - no action taken
The branch check after the delay is your safety net; even if unenrollment doesn’t fire in time, the contact still won’t be promoted unless the score is confirmed above the threshold at that moment.
Hope this helps!