What happens when a time-dependent action is in a queue and waiting for the right time to trigger and in between we edited the record and changed the condition after which original record no longer meets the triggering criteria?

Salesforce re-evaluates the rule criteria when a queued time-dependent action reaches its scheduled time. If the record no longer meets the rule’s criteria, the action is silently discarded — it doesn’t fire and no error appears anywhere user-visible.

The exact sequence

1. Record saves, rule criteria are TRUE, time-dependent action is queued for “+3 days”
2. User edits the record on day 1 such that criteria are now FALSE
3. The queue entry stays in the queue — the edit doesn’t remove it immediately
4. Day 3 arrives; the platform pulls the entry from the queue
5. Salesforce re-checks the rule criteria against the current record state
6. Criteria are FALSE → action is discarded silently

If the criteria flip back to TRUE before the scheduled time, the action will fire — the queue entry remembers nothing about the intermediate flip.

Why this design

The re-evaluation makes time-dependent actions self-correcting. Imagine:

• Rule: “If Case has been open more than 7 days, escalate.”
• Day 0: case created, criteria TRUE, escalation action queued for +7 days
• Day 5: agent closes the case
• Day 7: if there were no re-evaluation, the closed case would get escalated anyway — clearly wrong

So Salesforce checks the current state and skips when no longer relevant.

What if the rule itself was changed?

• Rule deactivated — queued actions are still in the queue but will not fire when their time arrives if the rule isn’t active
• Rule criteria modified — queued actions re-evaluate against the new criteria, not the criteria that were in effect when they were queued
• Rule deleted — queue entries are reaped

This second point catches admins out: changing the rule criteria can change the behaviour of actions that were queued under the old criteria.

What you do NOT have to do

• You don’t have to manually clean the queue when records become invalid — the re-evaluation handles it
• You don’t have to worry about stale queued actions firing on no-longer-eligible records

What you DO have to watch

• Records that flip in and out of criteria multiple times — the queue entry only fires once at the scheduled time based on state at that moment
• Time-dependent actions on deactivated rules — they may have left the queue, may still be there but inert; the safe pattern is to delete them explicitly when you deactivate the rule

What interviewers want

• The clear answer: re-evaluation at fire time
• The word “silently discarded” — no error, no notification
• Bonus: that modifying the rule changes how queued actions evaluate

Related

• How can we monitor pending time-based workflow actions?
• Can we delete pending time-based workflow actions?

Verified against: Salesforce Help — Time-Dependent Workflow Considerations. Last reviewed 2026-05-17 for Spring ‘26 release.