Currently, in FME Flow, when a user edits and saves an existing schedule, the scheduled job appears to run under the username of the last person who saved it, even though the ownership of the schedule has not changed. This behavior can cause issues when the last editor does not have the necessary permissions to access specific data sources or resources, leading to unexpected job failures.
We request that schedules retain the original owner's execution context, regardless of who last modified or saved the schedule settings. Saving or editing a schedule should not modify the account under which the schedule executes unless the schedule's ownership is explicitly changed.