Wait Event in Trigger #271
Description
Trigger-based flows are designed to run immediately and synchronously when a record is created, updated, or deleted. Because of this, Wait elements are not supported in these flows.
Salesforce explicitly prevents adding Wait events to trigger-based flows in the Flow Builder UI, since pausing execution would break the transaction model and could lead to inconsistent data or unpredictable behavior. As a result, it’s not possible to create this configuration through the UI under normal circumstances.
This rule in Lightning Flow Scanner exists to detect non-standard or programmatically created flows (for example, via metadata API or source control) where a Wait event may have been added despite UI restrictions. Such flows can cause runtime errors, failed transactions, or undefined execution behavior and should be refactored into an asynchronous flow type (such as a record-triggered flow with a scheduled path or a platform event–triggered flow).