A record-triggered flow starts when a configured record event occurs and its entry conditions match. A before-save flow is a good fit for changing fields on the triggering record. Related-record creation or updates need an appropriate after-save design. The timing is part of the behavior, not a cosmetic label.
Choose whether an update should run whenever conditions match or only when the record changes into the matching state. That transition guard can prevent repeated work on unrelated edits. Test a matching record, a nonmatching record, and a record that already matched before the update. Save and activate deliberately. A successful debug of a draft does not prove that the intended version runs for future events.