Back to all articlesAutomation design

Resolve overlapping conditions before choosing workflow branches

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A record can be urgent, incomplete, and already under review at the same time. If each condition starts its own branch, the workflow might request missing information while another branch closes the case. If only one branch runs, the result may depend on whichever condition happens to appear first in the builder.

To prioritize overlapping workflow conditions, separate eligibility from selection: identify every condition that is true, then apply an explicit rule that chooses one branch or permits a documented combination. Use exclusive branching when exactly one outcome is valid, explicit priority when several conditions can match but one must win, and intentionally parallel paths when their actions can safely coexist.

The practical test is simple: someone reviewing the record should be able to explain both why a branch ran and why another matching branch did not. The decision table below makes those explanations part of the design rather than a troubleshooting exercise.

1. Start with the actions that could conflict

Do not begin by rearranging conditions in the workflow builder. First list what each branch actually changes. Branches that look different by name may still compete for the same outcome.

For each candidate branch, record whether it changes a status, creates work, reserves a resource, sends a message, or ends further processing. Then identify actions that cannot both be correct for the same decision.

  • Competing final states: one branch closes the case while another marks it as awaiting information.
  • Competing instructions: one branch tells a person to wait while another asks them to act immediately.
  • Duplicate work: separate branches create equivalent review tasks.
  • Shared-state interference: one branch changes a field that another branch uses to decide what to do.

Classify each pair as incompatible, compatible, or unresolved. Treat unresolved pairs as excluded until someone can explain how their combined effects remain coherent. That is a conservative design choice, not a claim that every overlap is dangerous.

This inventory also exposes misleading branch names. “Urgent handling” may sound compatible with everything, but if it closes a record automatically, it is not merely an urgency marker. Rename or split it before deciding precedence.

2. Choose a selection rule, not an accidental order

Three patterns solve different problems. A workflow can use more than one pattern, provided each applies to a clearly defined group of actions.

Exclusive branching

Use exclusive branching when a record must have one outcome and the conditions can be defined without overlap. For example, “review open” and “review not open” form an exclusive split only if the review state is known. An unknown value still needs a fallback.

The advantage is a simple explanation: only one branch was eligible. The cost is that exclusions can become repetitive as conditions multiply. If every condition contains a growing list of exceptions, explicit priority may be easier to maintain.

Explicit priority

Use priority when overlap is legitimate but one primary action must win. Evaluate all relevant conditions against the same record state, then select the highest-priority eligible branch. Lower-priority matches remain visible as suppressed candidates.

The advantage is a compact policy for resolving ties. The cost is that a high-priority condition can repeatedly hide an important lower-priority condition. Document whether the suppressed action is abandoned, deferred, or reconsidered later.

Intentionally parallel paths

Use parallel paths when the actions have separate responsibilities and compatible effects. A primary path might select the next operational step while a companion path records an urgency marker.

Parallel does not have to mean simultaneous. It means the design permits both paths to run without one defeating the other. If the combined result depends on timing, use an explicit sequence instead.

3. Filled hypothetical branch decision table

Fictional worked example: A team processes internal service requests. The following conditions, branches, priorities, and records are hypothetical. They illustrate a recommended design, not a product capability or customer result.

The team uses four inputs: C means the request is closed, R means a review is already open, M means required information is missing, and U means the request is urgent. Each input must be known before normal selection begins.

The primary branch controls the next operational step. An urgency companion may run alongside it, but does not change the primary status or create another review task.

HYPOTHETICAL BRANCH CATALOGUE
Priority  Branch              Eligible when       Selected action
1         Closed stop         C = yes             End active processing
2         Existing review     R = yes             Retain current review
3         Information hold    M = yes             Create one information task
4         Standard work       Otherwise           Create one processing task

COMPANION PATH
Urgency marker: permitted when U = yes AND C = no.
Action: apply an internal urgency marker; no status change,
no additional review task, and no external message.

FILLED DECISION TABLE
Row  C    R    M    U    Primary selected     Companion permitted
A    yes  yes  yes  yes  Closed stop          None
B    no   yes  yes  yes  Existing review      Urgency marker
C    no   yes  no   no   Existing review      None
D    no   no   yes  yes  Information hold     Urgency marker
E    no   no   yes  no   Information hold     None
F    no   no   no   yes  Standard work        Urgency marker
G    no   no   no   no   Standard work        None
H    ?    any  any  any  Exception review     None
I    no   ?    any  any  Exception review     None
J    no   no   ?    any  Exception review     None
K    no   no   no   ?    Exception review     None

Decision contract: choose exactly one primary branch.
For this example, an unknown required input sends the record
to exception review before ordinary branch selection.
Rows H-K illustrate missing-input cases, not every combination.

The priority numbers represent business precedence, not a recommendation to rely on a visual top-to-bottom arrangement. The intended rule is: closed requests stop; otherwise preserve an existing review; otherwise resolve missing information; otherwise begin standard work.

The filled rows exercise the meaningful overlaps. They are not an exhaustive list of every possible input combination. Additional tests should include closed records with different remaining values and unknown values in more than one field.

4. Explain the excluded paths in plain language

A useful table states more than the winner. It explains what happens to other true conditions.

Row A excludes every active path. Although review, missing-information, and urgency conditions are all true, the closed state wins. This fictional process requires a separate, authorized reopening step before active work resumes. An urgency marker does not reopen the request.

Row B excludes the information-hold branch. Creating another task would split responsibility while an existing review is active. The missing-information condition is retained as context for that review rather than erased. If the review later ends and the request remains open, the next decision evaluates the missing-information condition again.

Row D excludes standard work. Urgency does not make incomplete information sufficient. The request remains on information hold while the companion marker makes its urgency visible. This prevents a high-urgency flag from silently bypassing a prerequisite.

Row F permits standard work and the urgency marker together. Their effects do not compete: one creates the processing task, and the other marks urgency. If the marker were changed to create another task or alter the primary status, the combination would need fresh review.

Rows H–K exclude ordinary processing. Unknown is not treated as false. The exception path identifies the missing input for human review without guessing the appropriate operational action.

These explanations are part of the decision contract. Without them, someone may later “fix” a suppressed branch by enabling it in parallel and reintroduce the original conflict.

5. Specify when the decision is made and revisited

Even a clear priority list can produce inconsistent results if branches read different versions of the record. Establish a decision boundary: the point at which the workflow gathers the inputs used for one selection.

In the hypothetical design, selection uses a single recorded set of input values. Branch actions do not cause the same decision to select additional primary paths. A later relevant change can start a new decision, subject to the workflow's entry rules.

Distinguish two situations:

  • A suppressed condition remains true: missing information was present during an existing review. Reconsider it when the review ends, rather than launching a second primary path immediately.
  • The record changes before an action begins: a request selected for standard work becomes closed. Recheck the action's prerequisites and stop or re-evaluate rather than acting on stale eligibility.

Also decide what happens when evaluation repeats without a meaningful change. Re-evaluation should not create another equivalent task simply because the workflow ran again. Define how existing work is recognized and how a repeated selection becomes a no-op or an update.

These are operating requirements to verify in the implementation. A decision document alone does not make the workflow enforce them.

6. Test combinations and recovery, not just individual branches

Testing each condition separately will miss the problem this design is meant to solve. Start with the filled rows, then test changes over time and partial failures.

  1. All conditions true: confirm that closed stop is the only selected path. Check that no active task or urgency companion is created.
  2. Review open and information missing: confirm that the existing review is retained, no duplicate information task appears, and the missing-information fact remains available.
  3. Information missing and urgent: confirm that information hold and the urgency marker coexist without starting standard work.
  4. No operational conditions true: confirm that the explicit default selects standard work, rather than leaving the record stranded.
  5. Unknown input: confirm that exception review identifies the missing value instead of interpreting it as a negative answer.
  6. Repeated evaluation: confirm that the same decision does not create duplicate work.
  7. State changes before action: close the hypothetical request after selection but before work begins; confirm that active work does not proceed on the old decision.

For a permitted combination, test partial failure too. Suppose the information task is created but the urgency marker fails. Retrying the whole combination could duplicate the task. Recovery should target the failed companion action or recognize that the primary action already completed.

If an incompatible pair has already run, pause further conflicting actions, establish which current state is authoritative, and send the case for human resolution where necessary. Record the selected rule and completed actions before restarting. Do not assume that reversing a status also reverses every consequence of the earlier branch.

7. Make precedence visible to the next maintainer

Keep the decision table beside the workflow specification and assign an owner who can approve changes. Record a rule version so that a past decision can be interpreted using the priorities that applied at the time.

A useful decision record contains:

  • The input values used for selection, including unknown values.
  • The eligible primary branches and the selected winner.
  • The precedence rule that excluded other matches.
  • Any permitted companion paths.
  • Which actions completed, failed, or were skipped.
  • Whether and why the decision should be revisited.

For hypothetical row B, the explanation could read: “Existing review selected because review takes precedence over information hold. Urgency marker permitted. No new information task created; missing information remains context for the current review.”

Where detailed decision logging is unavailable, use a controlled test sheet or review record. Do not describe a manually maintained record as an automatic audit trail. The objective is an observable explanation, using capabilities actually available in the workspace.

8. Use one overlap review as the next measurable action

Choose one workflow with competing outcomes and list every branch that changes its primary status or creates operational work. Build a decision table before changing its execution order.

For each meaningful overlap, require four answers: the winning primary branch, the permitted companions, the reason other paths are excluded, and the event that allows reconsideration. Give every unknown-input case an explicit destination.

Then run the test records and count three things: incompatible primary selections, unexplained suppressed paths, and duplicate actions after re-evaluation. Set acceptance criteria before testing; for this design, no tested record should produce incompatible primary actions or an unexplained tie.

Do not approve the workflow merely because its branches execute. Approve it when the observed selections match the table, failures have a defined recovery path, and another reviewer can explain the outcome without relying on undocumented evaluation order.

Workflow designAutomationBranching rulesDecision tables

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications