What's new
Workflow steps with conditions now have a "When hidden by condition" setting with two options:
Skip (default) — if the step's condition isn't met, the step is hidden and the stage's "Automatically move to stage" setting can fire without waiting for it. This is exactly how conditional steps have always worked, so nothing changes unless you turn the new setting on.
Wait to resolve — the stage's auto-move will wait until the step's condition resolves, instead of skipping past the hidden step.
Why we added it
Previously, if a step's condition couldn't be evaluated yet (for example, a balance field that hadn't synced from your accounting software), the step was treated as hidden and the auto-move could advance the process past it. In delinquency workflows, this could move a process to "Payment Made in Full" even though the tenant still owed rent.
At the same time, many workflows rely on the skip behavior intentionally — for example, a conditional "Change Stage" step that routes the process one way when the condition is true, with the stage's auto-move acting as the fallback when it's false. That's why this is a per-step setting rather than a global change: you choose which steps should wait and which should skip.
How to turn it on
Visual editor: open the step's settings and set When hidden by condition to Wait to resolve.
Classic editor: click the hourglass icon on the step (next to the other step toggles). When the flag is on, the hourglass appears in the step summary.
The setting stays in sync between both editors.
Example
Imagine a Grace Period stage with an auto-move to "Payment Made in Full" and two conditional steps:
Step A: "Send reminder email if unit is occupied" — a normal skip-when-not-applicable step. Leave it on Skip.
Step B: "Move to Late Rent if balance > 0" — you want the process to wait until balance data is available. Set it to Wait to resolve.
On a vacant unit's process, Step A hides and is skipped as usual. But on any process where the balance hasn't synced yet, Step B holds the auto-move until the data resolves, then the process either moves to Late Rent (balance owed) or continues to Payment Made in Full (paid).
Each step follows its own setting, even within the same stage — turning it on for one step doesn't make the process wait on everything.
What this setting does NOT do
It does not change any behavior while it's set to Skip (the default).
It does not wait on steps that are already completed or explicitly skipped.
It does not affect steps without conditions, there's nothing to hide.
It does not make manual-trigger steps fire automatically.
Do I need to do anything?
Only if you have conditional steps that should block a stage's auto-move, most commonly Change Stage steps in delinquency processes that check a balance. For those steps, switch "When hidden by condition" to Wait to resolve. Everything else can stay as-is.