## TL;DR

Deals stall when the advancing workflow skips them: missing required properties, failed enrollment, or a faulted action. Pick a stuck deal, walk it through the workflow's requirements, fix the gap, and re-enroll. Then fix the pattern so the next batch flows.

## Error

```text
(No error; the symptom is deals in one stage for weeks with an active advancing workflow.)
```

## Steps

1. Open a stuck deal and check the workflow's enrollment history for it. Expected: enrolled, skipped, or never evaluated.
2. Check the workflow's required properties against the deal; a missing close date or amount often blocks stage actions. Expected: you find the missing property.
3. Check the workflow's fault and skip logs. Expected: the reason it did nothing.
4. Fill the missing data or fix the trigger, then manually enroll the stuck deals. Expected: the backlog advances.
5. Add the required-property check to whatever creates deals. Expected: new deals arrive workflow-ready.

## When to use

- Deals pile up in one pipeline stage.
- An advancing workflow exists but stages never change.
- After adding required properties to a stage.

## When not to use

- Salesforce opportunity stages (different platform).
- Reps manually stalling deals (process, not automation).

## Tool compatibility

- HubSpot workflows and deal pipelines.
- Required deal properties per stage.

## Variant phrasings

### deals not advancing in pipeline

Enrollment or data gap; walk one deal through.

### workflow skipping deals

Check required properties and suppression.

## Why it happens

Stage automation assumes complete deal records. Real deals arrive incomplete, and the workflow silently skips them instead of complaining, so the stall looks like the workflow is broken when the data is.

## Edge cases

- Moving a deal backward can re-trigger workflows unexpectedly; check re-enrollment.
- Required properties differ per pipeline; a deal moved between pipelines can stall.
- Workflow action faults on one deal do not block others, so the stall can be partial.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oygJO1r7xj4F10EWATcrHA