When 'State Changes' Condition Is Evaluated in Notifications
This SNOW-CSA practice question tests your understanding of application rules, acl and notifications. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Notification 'Incident Assignment' configuration:
Table: incident
When to send: Record inserted or updated
Condition: state changes AND assigned_to is not empty
Who will receive: Assignment group
Email template: incident_assigned
sys_trigger record:
name: Notification - Incident Assignment
next_action: 2023-01-15 14:00:00
state: waiting
document: sys_notification_trigger
Refer to the exhibit. An incident is created with state 'New' and assigned_to is empty. Later, the state is changed to 'In Progress' and assigned_to is set to 'user1'. The notification does not fire. Which is the most likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Exhibit
Notification 'Incident Assignment' configuration:
Table: incident
When to send: Record inserted or updated
Condition: state changes AND assigned_to is not empty
Who will receive: Assignment group
Email template: incident_assigned
sys_trigger record:
name: Notification - Incident Assignment
next_action: 2023-01-15 14:00:00
state: waiting
document: sys_notification_trigger
A
The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire.
For timed notifications, the condition is evaluated when the trigger executes. If the state hasn't changed (i.e., it still is 'In Progress'), the condition 'state changes' will be false because it compares to previous value. Since the state changed earlier, at trigger time the field may not have changed from the last value. Actually, 'state changes' is a condition that checks if the field changed during the update that caused the trigger. For timed notifications, the condition is evaluated at the time of the trigger, and 'state changes' might not be true if the field hasn't changed since the trigger was created. This is a common pitfall.
B
The notification's 'Who will receive' is set to assignment group, but the assignment group is empty.
Why wrong: The assigned_to is not empty, but assignment group might be empty. The question does not provide assignment group info.
C
The notification condition requires the state field to change, but the state changed from 'New' to 'In Progress', so it should fire. The trigger is scheduled for later, so it will fire at that time.
Why wrong: The trigger is scheduled; it will fire later, but the question says it does not fire, implying it never fires.
D
The notification is configured to send only on insert, not on update.
Why wrong: It is set to 'Record inserted or updated'.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire.
Option A is correct because the notification's condition includes 'state changes', which is evaluated at the time the trigger runs, not at the time of the update. In ServiceNow, when a notification is configured with a condition that checks for a field change (e.g., 'state changes'), the condition is evaluated when the scheduled trigger executes, not when the record is updated. If the trigger is scheduled for a later time (e.g., via an asynchronous business rule or scheduled job), the condition may no longer be true because the state has already changed and is no longer 'changing' at that moment, causing the notification to not fire.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire.
Why this is correct
For timed notifications, the condition is evaluated when the trigger executes. If the state hasn't changed (i.e., it still is 'In Progress'), the condition 'state changes' will be false because it compares to previous value. Since the state changed earlier, at trigger time the field may not have changed from the last value. Actually, 'state changes' is a condition that checks if the field changed during the update that caused the trigger. For timed notifications, the condition is evaluated at the time of the trigger, and 'state changes' might not be true if the field hasn't changed since the trigger was created. This is a common pitfall.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The notification's 'Who will receive' is set to assignment group, but the assignment group is empty.
Why it's wrong here
The assigned_to is not empty, but assignment group might be empty. The question does not provide assignment group info.
✗
The notification condition requires the state field to change, but the state changed from 'New' to 'In Progress', so it should fire. The trigger is scheduled for later, so it will fire at that time.
Why it's wrong here
The trigger is scheduled; it will fire later, but the question says it does not fire, implying it never fires.
✗
The notification is configured to send only on insert, not on update.
Why it's wrong here
It is set to 'Record inserted or updated'.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common trap is the misconception that notification conditions are evaluated at the time of the record update, when in reality they are evaluated at the time the notification trigger executes, which can be asynchronous and cause conditions based on field changes to fail.
Detailed technical explanation
How to think about this question
ServiceNow notifications use a condition builder that evaluates field changes via the 'changes()' operator, which checks if the field value was different before and after the update at the time of the database operation. However, when a notification is triggered asynchronously (e.g., via a scheduled job or delayed queue), the condition is re-evaluated against the current record state, not the state at the time of the update. This means if the condition requires a field to have changed, but by the time the trigger runs the field has been updated again or the change is no longer detectable, the condition fails silently. This behavior is critical for understanding why notifications with 'state changes' may not fire when combined with delayed triggers.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the SNOW-CSA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Application Rules, ACL and Notifications — This question tests Application Rules, ACL and Notifications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire. — Option A is correct because the notification's condition includes 'state changes', which is evaluated at the time the trigger runs, not at the time of the update. In ServiceNow, when a notification is configured with a condition that checks for a field change (e.g., 'state changes'), the condition is evaluated when the scheduled trigger executes, not when the record is updated. If the trigger is scheduled for a later time (e.g., via an asynchronous business rule or scheduled job), the condition may no longer be true because the state has already changed and is no longer 'changing' at that moment, causing the notification to not fire.
What should I do if I get this SNOW-CSA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SNOW-CSA practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CSA exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.