Skip to main content
Open

Ensure Scheduled Jobs Always Run Under the Original Owner’s Account, Regardless of Subsequent Edits

Related products:FME Flow
  • April 28, 2025
  • 4 replies
  • 129 views

macatsafe
Safer

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.

4 replies

ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • April 29, 2025

nathanatsafe
Safer
Forum|alt.badge.img+9
NewOpen

jjf
Participant
Forum|alt.badge.img+1
  • Participant
  • August 3, 2025

The same behaviour is seen when a user enables Schedules also when I tested in v2024.2.3


gaplin_oz
Contributor
Forum|alt.badge.img+7
  • Contributor
  • October 23, 2025

This FME Forum is also related. FME Flow and scheduling jobs as alternate user account | Community.

We use automations extensively.  We have an inbuilt account we assign ownership of various items to rather than individual ownership.
However, It’s against our cyber standards to be logging on as this account to edit automations to ensure they run as the inbuilt account rather than an individual editor who can leave then cause automations to fail when their account id disabled.

Please consider. This is is security issue for us. Thanks