Skip to main content
  • EN

Hi all,

 

We upgraded from FME Server 2021.1.5 to 2022.1.1 a little while ago and since then our automations no longer seem to be triggering jobs. Each of the automation logs shows a scheduled trigger event at the correct time, but no jobs are getting queued. Manually triggering an automation also does nothing, apart from showing a green 'Automation triggered' message in the web interface and adding a successful event to the automation log.

 

Everything else about the server seems fine. Schedules run at the time they're meant to and queue jobs up properly, and I'm able to run all of the workspaces that should be automated with no issues at all. All of the server logs I can find show no obvious errors and fmeserver.log shows no hint of any of the jobs being run due to automations.

 

I've tried uploading a completely fresh workspace to the server and setting up a new automation. The logs show the automation being assembled and actions being linked, etc. but this is subject to the same problem and doesn't work, so I'm a little stuck.

 

Has anyone else seen this behaviour and do you have any advice for finding the cause?

Hi @ti_m​ ,

 

This is a very curious issue, I've spoken with my team and it's not anything we've come across before so it will likely require more in-depth troubleshooting efforts than we can offer via the Community. Please can you submit a case here and include the following information:

  • Details on your FME Server deployment architecture e.g. express, distributed database/webapp/engines, fault-tolerant, Docker etc
  • Does this problem occur when you create a Schedule from the Schedules page as well, or only from within an Automation?
  • Please zip up and share all the log files.

Once we find a solution we can update this post with the answer in case any other users encounter it in future as well.

Has this ever been resolved? We are also having the same issue having updated from 2021 to 2023.

We appear to be having a similar issue after having upgraded from 2022.2 to 2024.

We appear to be having a similar issue after having upgraded from 2022.2 to 2024.

Hi. I took a look and I don’t see this as a known issue anywhere. The only thing I can think of is the owner of the automations didn’t get restored or doesn’t have the same permissions on the new system. But I’m not confident about that being the answer. I suggest you file a case with our support team to look into this. 

As mentioned in the above answer, please include the following information:

  • Details on your FME Flow deployment architecture e.g. express, distributed database/webapp/engines, fault-tolerant, Docker, etc.
  • Does this problem occur when you create a Schedule from the Schedules page as well, or only from within an Automation?
  • Please zip up and share all the log files.

Regards

Mark

Chiming in to say that I’m having the same issue.  If anyone solved this and could point me in the right direction, that would be great.

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
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.