In the last few months we've noticed that users have been running into issues with flows that reassign record ownership or share record access. For example, we have a record-triggered flow that assigns certain types of cases to a queue. However the flow fails to run because when the case is assigned to the queue the users looses access to it, which is expected. My understanding is that because the flow runs in system context it should be able to update ownership to the queue and save it, and the creator would loose edit access to the case afterwards. We have not made any changes to this process, but this is not working as expected anymore. The only way I have found to resolve this is by granting the user modify all access to cases. We've experienced similar things in other orgs where we have automations that are updating record owners or are triggered when the record owner changes. It's possible I am missing something, but it seems like record-triggered flows are no longer running in system context. Has anyone else noticed this behavior recently?
#Flow
Have you verified that the flow is actually running via user debug? Perhaps the user does not have the run flow permission and the flow is not running? Also, debug logs may shed light on the problem.
