An automation rule has three parts: a trigger, conditions and actions. The trigger is the event that makes the rule look at a work item at all. Work item created fires once, when the record is saved for the first time. Work item updated fires when someone edits a field. Work item transitioned fires when the status moves along a workflow path.
Pick the trigger from the moment in the process, not from the field you want to change. If a request must be routed the moment it arrives, a created trigger is right; an updated trigger would wait until somebody edits it, and might never fire. A rule that should react to a status move needs the transitioned trigger plus a status condition.
In this practice site a rule runs once per event, in the order rules were saved, and its result goes into the audit log. Scheduled triggers, branching and smart values are not part of the local model; the lessons say so where a hosted rule would use them.
Match the rule trigger to the moment in the process.