All topics
English

Workflows · 3 min read

Filter records and control behavior after a wait

Combine conditions and understand why a record may stop before subsequent actions.

In this guide
  1. Configure Conditions
  2. Compare all versus any
  3. Use Wait for a follow-up sequence
  4. Define a useful outcome
  5. Related guides

For Insurance agency Owners and administrators.

Configure Conditions

  1. Open Conditions. Without filters, every triggering record can continue.
  2. Click Add filters or Edit filters. Select field, operator and value as in record lists.
  3. Apply and review the builder summary. Canceling does not apply changes.
  4. With multiple conditions, choose Match all or Match any.
  5. Check the Conditions node and review before saving.

For documents, use outstanding DMI count greater than zero. For renewal, add Status = Active. Every condition should serve a purpose rather than merely being available.

Only records with outstanding DMI greater than zero.
Only records with outstanding DMI greater than zero. Open the image to enlarge it.

Compare all versus any

ConfigurationResult
All: Status = Active and DMI > 0Only active policies with outstanding documents.
Any: Status = Active or DMI > 0All active policies, even without outstanding documents, plus others with DMI.

The second choice may greatly expand the audience. Compare record values with an equivalent filtered list before activating. Filters are not a frozen client selection; each event is evaluated against workflow conditions.

Use Wait for a follow-up sequence

Add Wait between actions and choose minutes, hours or days. Example: create Task and send guidance, wait two days, then notify the service channel. The run stays Waiting without requiring the page to remain open.

At resumption, the record must still match the filters. If DMI becomes zero, subsequent steps are skipped. Waiting does not prove reading, a reply or Task completion; filters must represent the outcome that matters.

New changes can start other runs while one waits if frequency permits. Use tracked fields and conditions to reduce unnecessary triggers; Wait is not a global client lock.

Two-day wait before the next step.
Two-day wait before the next step. Open the image to enlarge it.

Define a useful outcome

For document follow-up, the Task should tell its assignee to check the record and record the outcome. An internal notice should include client name and record link without unnecessary data. If the agency does not update outstanding fields, the flow cannot know documents arrived.

Use history to distinguish unmet conditions from delivery failure. A step skipped because the issue was resolved may be correct. Removing filters merely to continue one run changes the rule for all records.

Related guides

Reviewed October 26, 2026.