Hi all! I have two after-save record-triggered flows. The first fires on record creation. Someone signs up for a volunteer shift, it checks their eligibility, then updates the Status field to Confirmed (or not) and notifies a staff member that a shift was either confirmed or needs manual confirmation.
The second flow is called on record update, when the Status field on the Volunteer Hours record changes to Confirmed. It sends an email confirmation to the volunteer and schedules an email reminder as well.
Up until the latest release, the first flow would trigger the second to fire. Now it does not. There are no errors in the second flow during debug, and it works as intended when the status is manually changed to Confirmed. The problem is only occurring when the status is changed via the other flow. Any suggestions?
#FlowMichael Brown (Salesforce) 
Forum Ambassador
Hi Mandie,
I would check the Flow Trigger Explorer and make sure that your Update After Save flow is firing after your Record Create flow, just as a precaution.
Also, for same record updates, using a before save flow is recommended, so that could be an option to try. Have a before save flow set the status to Confirmed, which will run before your after save flow, the latter of which should then recognize the Confirmed Status.
You could also potentially clone the email action into your record create flow, because I could see the Status field as not being treated as an update, since it's being "updated" at the time of creation.
Thanks,
Mikey
