Hello,
I recently made some updates to my MQL workflow, and I’ve attached a screenshot of the updated workflow for your reference. However, for the past two days, I’ve been encountering an error related to the lifecycle stage.
Despite reviewing the links provided by HubSpot support, I’m still unable to pinpoint the exact cause of the issue. Could you please lend me your expertise and assist me in resolving this matter?
Your assistance in troubleshooting this error would be greatly appreciated.
Hey @YeshaMehta, thank you for posting in our Community!
Since lifecycle stages do update backward. Currently, to set the lifecycle stage backward via these tools, you will first need to clear the record’s existing lifecycle stage value. The value can be cleared manually or may be automatically cleared via a workflow or an integration that syncs contact data.
Could you please provide me with more details regarding the specific error message you’re encountering? Any additional context or screenshots related to the error would be helpful in identifying the root cause. I see the error message is cut.
Thank you,
Pam
Hi @YeshaMehta,
If you look up the contact that threw the error, you should notice that their Lifecycle stage is already progressed further than Marketing Qualified Lead. HubSpot by default wants contacts to move forward, not backward: Use contact and company lifecycle stages
Lifecycle stages are used to track how contacts or companies move forward in your process. Default automatic updates to the lifecycle stage property will only move the stage forward (e.g., no value to Subscriber, Subscriber to Opportunity, etc.).
You could by brute force empty the lifecycle stage value using the “Clear property value” workflow action but rarely is this what makes most sense. For example, if you have a Sales Qualified Lead or even a Customer with a score matching your enrollment criteria, you wouldn’t want them to be moved back and in that sense unqualified.
Instead, I’d recommend updating the enrollment criteria of your workflow to only enroll contacts with an empty lifecycle stage, subscriber, or lead. That would prevent the error from occurring and still have the intended effect.
Best regards
@YeshaMehta without having the full picture and being able to explore in your portal it’s hard to confirm that it will definitely solve the issue - but your updated criteria look good and I would think that no further errors are thrown, based on what I know. Best regards!
