What it requires. Record-triggered flows must not contain Wait elements or Scheduled Paths. Wait elements in record-triggered flows create Paused Flow Interviews that sit in the system consuming org resources and potentially holding record locks indefinitely.
Why it matters. A Paused Flow Interview holds a snapshot of the record at the time of pausing, which can conflict with subsequent record updates. Paused interviews also count against org limits, can prevent record deletion, and create operational overhead for administrators who must manage and resume or delete them manually. Scheduled logic in record-triggered flows should be implemented via Scheduled Flows instead.
How to fix it. Remove Wait elements and Scheduled Paths from record-triggered flows. Move time-based logic into a dedicated Scheduled Flow that queries for records meeting the criteria and processes them in bulk.
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.