A Workday condition rule that is not working almost always falls into one of nine causes, and the quickest way to find yours is to check them in this order: what kind of condition it is and whether its true or false result runs the step, which business process definition ran, the condition’s effective date, the Rule Tester report, the field values at that moment, the rule logic, how the event started, step security, and step order.
Kiweely Vine is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it reads the business process and its condition rules in the tenant and tests the step as the people it affects. See how it works below.
The step “did not fire” can mean four different things: the condition was evaluated false, a different definition without your condition ran, the step ran but landed with nobody, or conditions were never evaluated. Each check below separates one of them.
1. Which kind of condition is it, and what does true mean?
A condition belongs to a step and holds one or more rules. Workday states that when it has more than one rule and any is false, “the entire condition is false” (Concept: Step Conditions). The kinds differ in what a true result does:
| Condition | Available on | True means | False means |
|---|---|---|---|
| ConditionEntry | Available onEvery step except Initiation | True meansThe step runs | False meansThe step is skipped |
| ConditionWhile-running | Available onApproval Chain and Consolidated Approval Chain steps | True meansThe step routes to that approval level | False meansThat level is skipped, and the next is evaluated |
| ConditionExit | Available onApproval Chain and Consolidated Approval Chain steps | True meansThe step exits | False meansThe chain continues up |
| ConditionValidation | Available onInitiation and Action steps | True meansCritical: the step is blocked from exiting. Warning: the error shows, and you can continue | False meansThe step exits |
The most common “not working” report is inverted polarity: a rule written as “should this step run” is placed under Validation, or one written as “should this be blocked” is placed under Entry. Name the kind and read the rule as a statement about that kind. Also check the severity of a validation condition. Workday sets it to Critical by default.
A validation rule describes the invalid state: it is true when the data is wrong, and the step exits only when every validation rule is false. A rule that describes valid data (Cost Center is not empty) blocks every good submission. Three setup limits also stop a validation condition from working (Concept: Step Conditions):
- Workday allows a validation condition on the Initiation step only when the Business Process Configuration Options report shows Send Back in the Approval Options column, and on an Action step only when Send Back is in the Options on Save column of Allowed Actions.
- For a process that uses a defined template, such as Change Job, the roles that can initiate it also need View All on the business process security policy, or Workday does not evaluate the validation conditions.
- Maintain Step Conditions is not available from the Edit Business Process Definition page. Open the definition with View Definition and use the step’s related actions.
Validations on financial, payroll and costing transactions (Maintain Custom Validations) are configured outside the business process and are covered in Workday custom validations.
Some Action steps carry Workday-supplied entry conditions that you cannot edit. Both Workday’s conditions and yours are evaluated, and Workday skips any step that does not satisfy all the entry conditions. If your rule is true and the step is still skipped, a Workday condition may be the false one.
2. Which business process definition actually ran?
Your condition only counts if its definition ran. Four things change which one does (Concept: Business Processes and Organizations; FAQ: Business Processes):
- Workday chooses the definition by the initiation date of the event, not the event’s effective date. If you changed the definition effective 2020-08-10 and the event was initiated on 2020-08-09, the old version ran.
- When an organization has its own version of a process, the version on the parent is no longer available to it. Workday looks at the organizations associated with the object of the process.
- If the definition had a critical error as of the date the step was entered, Workday uses the default definition instead. A fix made the next day leaves no visible error on the event.
- For a saved-for-later event, the definition is set when you click Save for Later. If the fields tied to a rule-based definition’s conditions hold no data that satisfies any condition at that moment, Workday bypasses the rule-based definition and uses the default one (Concept: Rule-Based Business Process Definitions).
To see which one an event used, select Business Process, View Definition from the related actions menu of the event. To see the definition at the time the event started, enter the event’s start date in the Effective Date field.
3. Does the condition’s effective date cover this event?
Maintain Step Conditions prompts for an effective date, defaulting to the current date, and an optional time zone if the Business Process Configuration Time Zone check box is on in Edit Tenant Setup - System (Concept: Step Conditions). Workday’s own example: remove a condition rule on an Action step with an effective date of 2024-01-19, and it will not trigger on events initiated on or after 2024-01-19 in the tenant’s time zone. Events initiated before that date still trigger it.
A future date takes effect at midnight on that date in the chosen time zone. A past date takes effect at 11:59:59 PM on that date (Concept: Effective Dates). Both ways, an event already in flight keeps the rules it started under. Test a change on a new event.
4. What does the Rule Tester say?
Open the Rule Tester report from the related actions menu of the business process event. It shows the full execution flow of the condition rule, which helps you understand and troubleshoot results. Workday notes that it is not available for Workday-owned condition rules (Create Business Process Condition Rules).
Read where the evaluation stopped, not only the final result. A rule that “does not fire” is usually doing what the tester shows: it stopped on a row you did not expect to decide the outcome (check 6). If someone else wrote or changed the rule, including an AI assistant, the Rule Tester flow is the record of what Workday did; a description of the rule is not.
5. What values did the rule actually see?
Check the data on the event, not on the record as it is today. Workday’s FAQ gives two tools:
- From the related actions menu of the business process step, select Reporting, Report Fields and Values. It lists the values of each field used in the condition rule at the time the step executed.
- Create a custom report directly from the business process event and place the rule’s fields in it, calculated fields especially, to see where the rule breaks.
Three causes show up here:
- The wrong business object. Many fields share a name and belong to different objects. For a condition rule, a calculated field must be available on a business object related to the process, such as Worker Business Process or Action Event, and the FAQ describes building a chain of calculated fields to move data between objects (FAQ: Calculated Fields).
- Timing. In the Hire process, a worker-based field is not valid until the hire completes, because the pre-hire is not yet an employee (FAQ: Business Processes).
- Initiator. On an Initiation step, Workday recommends choosing a value other than Initiator in the Source External Field or Condition Rule prompt: “When you select Initiator before Workday initiates the business process, the field returns no results.”
If the field is a calculated field that returns nothing, the rule behaves as though it reads a blank. See why a calculated field returns blank.
A calculated field has its own order. Evaluate Expression evaluates its conditions in sequence, stops at the first true one, and returns the Default Value when none is true (Evaluate Expression). A field meant to say Manager returns the default, or the value of a broader condition higher in its grid, when your tenant’s data does not match the first condition you expected. Workday also states that calculated fields cannot be set up as eligibility rules for business processes (Setup Considerations: Calculated Fields), so moving the logic there does not make the process use it.
6. Does the rule logic say what you meant?
Workday examines the conditions in a rule, in the order you specify, until it finds a match. With And, it stops checking as soon as one condition is false. With Or, it stops as soon as one is true (Create Business Process Condition Rules). Two practical effects:
- Parentheses control mixed logic. Workday’s example is
(A and B) or C, which is not the same asA and (B or C), and nothing warns you if the grouping is wrong. - For a Yes/No field, the operator and the Comparison Value check box decide what true means together. Workday’s examples for testing that the field is true are equal to with the box selected, and not equal to with the box cleared. Equal to with the box cleared tests for false.
- A rule written with is empty or is not empty can pass the test you tried by accident. Test the case that should run the step and the case that should skip it, each on its own event. A rule that passes only the positive test has not been proven.
Test each rule inside a condition one at a time, and each condition on a step with several one at a time (FAQ: Business Processes).
What the Rule Tester shows when the logic is the problem:
| You expected | Rule Tester shows | Fix |
|---|---|---|
| You expectedA later And row to decide | Rule Tester showsEvaluation stopped at an earlier false row | FixPut the row that should decide where it is read, or move the other check to a different step, then test both cases again |
| You expectedA later Or row to rescue a false early row | Rule Tester showsEvaluation stopped at an earlier true row | FixRemove or narrow the early true condition |
| You expected(A and B) or C | Rule Tester showsNo parentheses, so the grouping is not what you meant | FixAdd parentheses |
7. Was the process started in a way that skips conditions?
Workday states: “Conditions aren’t evaluated when a business process runs from a web service or EIB and is set to automatically complete.” When a web service automates a process, as in an EIB spreadsheet upload, Workday skips Approval steps automatically but still evaluates entry conditions for Integration steps, Service steps and Action steps that initiate sub-events (Concept: Step Conditions). If the step “does not fire” only for loaded transactions, this is the cause.
8. Did the step run, but reach nobody?
A rule that is correct can still look broken from the initiator’s side:
- Workday says that when a report field is used in a rule, it evaluates the security of the field if the security logic is part of the field itself. If the processing user does not have access to fields or values for the next step, the step is skipped (Create Business Process Condition Rules). A tester with broad access sees the step fire, so retest as the person who processed the previous step, through a proxy in a non-production tenant. See Test Rule says Yes but the step still skips.
- A task is unassigned when the specified security group contains no user, or only users with disabled Workday accounts. A user with a future hire date makes it unassigned, as does a disabled, expired or locked account. Run the Unassigned Tasks report, filtered by process and date range (FAQ: Business Processes).
- A change to the process’s security policy can remove access to a task already in someone’s My Tasks. The task stays assigned but can no longer be opened, and someone must reassign it.
9. Does step order interfere?
Steps are ordered by letter: Initiation is always a, and steps with the same letters run in parallel, in any order, and must all finish before the next letter starts. For condition rules, Workday says not to give steps the same character strings in the Order column (Concept: Order of Execution). Workday sorts numbers sequentially, not numerically, so 10 sorts before 2. Use letters. A skipped step that you expected to follow another may be running in parallel with it.
Worked example: a comment requirement that does nothing
Based on Workday’s No Show example, with one change. The goal is that HR Partners must add a comment when they review each No Show. Workday’s configuration: a condition rule with Source External Field or Condition Rule Comments, Relational Operator is empty, then, under Maintain Step Conditions with the effective date set to today, a row under Validation Conditions on step b) Action (Example: Create Business Process Condition Rules).
Suppose, in this illustrative case, the administrator selects the rule under Entry Conditions instead.
| Step | Result |
|---|---|
| StepEntry condition: Comments is empty | ResultComments is empty when the step is reached |
| StepCondition is true | ResultStep b) runs, as it would anyway |
| StepHR Partner reviews and leaves the comment blank | ResultNothing blocks the step |
The rule evaluates correctly and does nothing useful. Run through the order on a test event:
- Kind: Entry. The rule’s job is to block the step from exiting, which is a Validation condition’s job. Polarity found.
- Definition: View Definition on a test event shows the intended definition ran.
- Effective date: today, so new events use it.
- Rule Tester: shows the rule evaluating exactly as written, so the logic is sound and the placement is wrong.
Moving the rule to Validation Conditions, with the default Critical severity, blocks b) until Comments is filled in, and the same rule now does its job. Test the negative as well: a comment added, and the step exits.
Worked example: an And rule that stops before the check that matters
An illustrative case. The design says a step adds an extra approval only when the worker’s calculated status is Manager. The rule is an And: its first row checks a location, the second checks the calculated field for Manager. On a report, the calculated field correctly returns Manager for the worker.
Rule Tester shows the And stopped on the location row, which is false for this worker. The Manager row was never read. Adding another copy of the Manager row at the bottom changes nothing. Decide whether the location belongs in this rule at all; if it does not, move it to a different step’s condition, then test a manager in that location, a manager outside it and a non-manager.
If the same rule sat on the Initiation step with Initiator as its source, Rule Tester would show no value for that row, because Initiator returns no results before the process starts. Reordering rows does not fix that; changing the source does.
What is the order to check, in one list?
- The condition’s kind and what true means.
- The definition the event used (View Definition).
- The condition’s effective date against the initiation date.
- The Rule Tester report.
- Report Fields and Values on the step.
- And/Or grouping, then positive and negative tests.
- How the event started: web service or EIB.
- Step security, skipped steps and Unassigned Tasks.
- Step order letters.
A rule changed in a Sandbox does not change Production until the configuration is moved there. If a copied condition fails only in another tenant, see copying Workday configuration between tenants. For steps that sit in My Tasks, see business process awaiting action.
Kiweely Vine is a desktop AI agent for Workday that can answer Workday questions and read a client’s tenant with consent.
Where Kiweely fits
Kiweely Vine is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It reads a business process and its routing in your tenant, changes it, and tests it as the real people through Start Proxy.
In a recorded run in Kiweely’s own Workday Development tenant (with fictional sample data, not a customer result), Vine built a training-approval Extend app from a plain request, set up its access (Employee As Self, Manager) and the approval’s business process security policy, activated the security changes, added the Manager step to routing, and tested it as the employees and managers through Start Proxy. It took 1 hour 51 minutes from sign-up to the checked result, and the film reports five checks passed (watch the film).
Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant (pricing). Start free.
Frequently asked questions
How do I test a Workday condition rule?
Open the Rule Tester report from the related actions menu of the business process event. It shows the full execution flow of the rule. It is not available for Workday-owned condition rules.
Why was my step skipped when the condition looked true?
Check the polarity: an entry condition that is true runs the step and false skips it, while a true validation condition blocks or warns. Then check the field values Workday used, under Reporting, Report Fields and Values on the step.
Do condition rules run when a business process starts from an EIB or web service?
Workday says conditions are not evaluated when a business process runs from a web service or EIB and is set to automatically complete. Entry conditions are still evaluated on Integration, Service and Action steps that initiate sub-events.
Does changing a condition rule affect events already in progress?
No. The effective date you set on Maintain Step Conditions is respected, and Workday uses the condition in force for events by their initiation date. Initiate a new event to test the change.
Why does the business process use the default definition instead of mine?
Workday falls back to the default definition when the definition had a critical error as of the date the step was entered, and, for a rule-based definition, when a saved-for-later event has no data that satisfies any condition.
Does the order of rows matter if every row is true?
Yes for Or, because the first true row decides and the rest are not read. For And, a later false row fails the rule only if every earlier row was true. Test with events where one row is false and confirm in Rule Tester where evaluation stopped.
What should a defect report about a condition rule include?
The event, the Rule Tester flow, the order of the rows, the calculated field grid if one is used, and whether the test ran as the processing user or as an administrator. That lets someone else reproduce the miss.
Sources checked
- Concept: Step Conditions
- Create Business Process Condition Rules
- FAQ: Business Processes
- Concept: Business Processes and Organizations
- Concept: Rule-Based Business Process Definitions
- Concept: Effective Dates
- Concept: Order of Execution
- Example: Create Business Process Condition Rules
- FAQ: Calculated Fields
- Evaluate Expression
- Setup Considerations: Calculated Fields