Error after upgrade Flow 2026.1

Are you able to trigger a job via an automation?

Normally when I’ve seen this it’s been a certificate issue

See this article

FME Flow Run Workspace: There was an error submitting the job – FME Support Center

Yes, i am able to trigger job via automation 
Because i updated Flow from version 2024.2 to 2026.1 , and all apps and automations worked on previous version, but right now i am having problem with flow apps only
Automations that worked on previous version, they work in new version too

There could be a variety of issues occurring here. Theres some additional articles to check here: FME Flow Troubleshooting Guide – FME Support Center

I agree with ​@ebygomm that its likely a certificate issue, possibly also related to dns and routing configurations.

One thing I always find worth checking is going onto the machine that FME Flow is installed/running on and trying to browse to the url you expect to point towards FME. If it works and doesn’t come up with any errors, then that narrows down the problem.

If it doesn’t work, or comes up with ssl issues, then that’s a good place to start looking.

​@hkingsbury Thank you for your answer, i will try that

Hi ​@simeon.simic,

Are you able to run Samples/AustinApartments.fmw with the Job Submitter service? If so, you may have encountered this deprecation.

If not, I’d next if check the Service URLs have been updated after configuring HTTPS. Do this from System Configuration > Network & Email > Services:

In almost all instances, the hostname should match the hostname you use to access Flow. It should be HTTPS if you use HTTPS to access Flow also.

If this isn’t the issue, check for any mention of “PKIX path building failed” within the either of these logs:

• Resources/logs/tomcat/[hostname]/localhost.[today].log 
• Resources/logs/tomcat/[hostname]/catalina.[today].log

If this appears, you need to import the certificate into the truststore. See this KB article for guidance on this.

If neither of these are the root cause, we’d need to take a look at logs so submitting a support ticket would be the best way to go. If you do this, please include:

• Your Flow deployment type (Express, Fault-Tolerant, Distributed).
• Your Flow build number.
• All logs within Resources/logs/tomcat/[hostname]/.
• Resources/logs/core/current/fmeserver.log.

Hopefully we can get this resolved!