Skip to main content
Question

Automations last edited by and running Jobs

  • August 24, 2026
  • 4 replies
  • 26 views
j.botterill
Evangelist
Forum|alt.badge.img+65

I have automations owned by ‘admin’ (superuser).

If I come with another user that has full access, stop the automation make changes, save and enable again…. I find the next scheduled run under the Job logs, it is then run under the username that last edited it.

  • this can lead to issues if the dependent components like run workspace > connections etc are also not granted permissions to that user

I’m using 2026,1 … was this always the case or does the owner of the automation run the job? Maybe this change in the FME REST api v4 ?

 

    4 replies

    david_r
    Celebrity
    • david_rCelebrity
    • August 24, 2026

    I think this was always the case. The obvious workaround would be to share the dependencies with the automation editor(s), if possible. Otherwise you could possibly use the REST API to automatically change the owner back to Admin every time before the automation runs.

      redgeographics
      VIP
      Forum|alt.badge.img+64

      This issue has been around from pre-v4 API and it’s especially annoying when an admin stops and starts an automation (for example as part of an upgrade), then the user can’t see their own job logs anymore.

      FME rocks! \m/
        ebygomm
        Evangelist
        Forum|alt.badge.img+53
        • ebygommEvangelist
        • Evangelist
        • August 24, 2026

        It’s been that way since at least FME 2021

        Identify the User that will run workspaces within an automation | Community

          ebygomm
          Evangelist
          Forum|alt.badge.img+53
          • ebygommEvangelist
          • Evangelist
          • August 24, 2026

          I think this was always the case. The obvious workaround would be to share the dependencies with the automation editor(s), if possible. Otherwise you could possibly use the REST API to automatically change the owner back to Admin every time before the automation runs.

          The owner doesn’t change when someone else starts an automation, it still is owned by admin but run by the last person to start it. You have to stop and restart the automation as Admin if you want the automation to run as admin. Part of the issue, is that someone can stop and start an automation and you don’t know who it is going to run as until it actually happens.

            Community Stats

            32,847
            Posts
            124,579
            Replies
            41,424
            Members
            Terms & ConditionsAccessibility statement
            A product of
            Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.