topic Re: 2 workflows with the same trigger but different schedule in Lists, Lead Scoring & Workflows

2 workflows with the same trigger but different schedule

hphan-trlaw — Fri, 12 Dec 2025 01:59:12 GMT

Hi,

I have 2 workflows for when someone submits the form. If it's during business hours, it will edit the record of a contact's property to A. If it's outside working hours, it will be B.

However, it looks like the workflow, although scheduled to run at specific times only, still records the trigger during the off-time and then runs it when it's on-time, overwriting the previous property value.

I don't think it's possible to combine 2 workflows into one and branch out based on hours of the day and days of the week. Is there a way to prevent this, or a workaround?

Thanks in advance.

Re: 2 workflows with the same trigger but different schedule

karstenkoehler — Fri, 12 Dec 2025 04:59:41 GMT

Hi @hphan-trlaw,

You can use enrollment in either workflow as an unenrollment trigger in the other 🙂

Alternatively:

Add those contacts to a static list, then use the list as an unenrollment trigger
Set a property at the end of the workflow (or use an existing action at the end of the workflow) to unenroll

The logic is always the same: the state of the contact at the end of either workflow should make them ineligible to enroll in the other.

Best regards

Re: 2 workflows with the same trigger but different schedule

hphan-trlaw — Fri, 12 Dec 2025 05:16:31 GMT

Can you explain a bit further on how to use the enrollment of one workflow as the unenrollment trigger in the other? Is the contact technically enrolled in two workflows simultaneously, even though they have different schedules?

Re: 2 workflows with the same trigger but different schedule

karstenkoehler — Fri, 12 Dec 2025 05:22:39 GMT

@hphan-trlaw you have different options for unenrollment settings in workflow, explained in detail here: https://knowledge.hubspot.com/workflows/set-unenrollment-triggers-in-company-deal-ticket-quote-based-workflows#manage-unenrollment-in-contact-based-workflows

And yes, the schedule simply says when to execute the actions. If the enrollment criteria still hold true, the workflow is really still supposed to enroll. (If it didn't, it wouldn't do it's job, right?) So you need to tell it, in a way, that what it's supposed to do has already been taken care of by the other workflow.

Could also be done with a branch at the beginning of the workflow that checks if the desired action was already completed (assign owner, send email, set date stamp etc).