Why a workflow did not run

1. Check that the workflow is published and active

Open the workflow and confirm it has a valid published version and is switched on.

Remember:

• Save only updates the draft
• Review & publish / Update creates the executable version; and
• turning a workflow off stops new matching.

If dashboard activation is blocked, open the workflow and resolve the validation message first.

2. Check that the trigger event actually happened after publishing

For record-created or property/stage-change triggers, confirm the relevant HubSpot event happened after the workflow was published and active.

Examples:

• a Contact was actually created after activation
• the watched property genuinely changed
• the Deal or Ticket moved stage after activation.

A record already sitting in a matching state is not the same as a new change event.

3. Check the trigger configuration

Open the trigger inspector and review every portal-specific selection.

HubSpot configuration can change after a workflow is published. A form, owner, stage or property that was renamed, archived or removed can leave the workflow referring to stale metadata.

Run Sync Kanopee with HubSpot and review the trigger if anything appears missing or outdated.

4. Check plan restrictions

If the workflow uses a Pro-only trigger or you are at the Free active-workflow limit, Kanopee should block activation/publishing rather than silently run an unsupported configuration.

Check the account plan if the workflow cannot be turned on or published.

5. Check trigger-specific requirements

For Form submission workflows:

• confirm the form is synced and selected
• confirm the workflow is Pro and active
• confirm the submission happened after publication; and
• reconnect HubSpot if form access is stale.

For Scheduled workflows:

• confirm Pro
• check frequency, weekday/custom interval and timezone
• review enrollment criteria.

Use the dedicated trigger article for the full checklist.

6. Check the Enrollment tab

Open the workflow's Enrollment tab.

If the record is absent, focus on the trigger, workflow status and integration event.

If the record is present, the problem may be later in execution—for example a delay, a failed HubSpot action or a workflow that was switched off before a delayed resume.

7. When support should investigate

Contact support when the configuration checks pass but a reproducible new event still does not create the expected run.

Provide:

• the workflow name
• the trigger type
• the approximate time you expected the event to occur; and
• whether the record appears in the Enrollment tab.

Do not send HubSpot access tokens, passwords or secret credentials.

---