Goal: make one predictable update when a record changes.
For a task tracker, a useful first rule might set a follow-up flag when a task enters a particular status. Choose fields that actually exist in your app.
“When a task changes, if its status is Waiting, set Needs follow-up to Yes.” This identifies the event, condition, and action before you configure anything.
If the fields or operation you need are not offered, inspect the available features rather than assuming any external service or multi-step workflow is supported.
Record-event rules support bounded conditions and actions; this is not an unrestricted automation engine. Date-based behavior has different execution requirements, so do not treat it as a guaranteed continuously running scheduler. Preview email behavior does not establish delivery of real messages.
Check access and inspect what the rule changed before adding another rule. A successful result should be understandable without guessing which automation ran.