It should really just be an API call to FME Flow, nothing version-specific about that. As a workaround, can you try sending the API call with a HTTPCaller?

If that doesn’t work either, my bet is firewall/network issues.

Hi Red.

No, I don’t think so.

I edit the two workspaces in 2020 desktop and 2024 form, both running on the same pc.

One workspace (2020) works, and connects to our 2022 server without problem. The other workspace (2024) doesn’t.

So it’s not a firewall/network issue as far as I can see. It’s more likely an issue with 2024 form.
I will talk to IT just in case.

And as for an API call, I really cannot replicate this, since I’m editing a transformer in a workspace, not calling the REST interface myself.

Cheers.

Hi @lifalin2016 

Forwards compatibility, such as using a workspace authored in Form 2024 and running on Flow 2022 is not something we support. Our Knowledge Base article FME Versions and Workspace Compatibility goes into more detail if you are interested. 

Is there something particular about 2024 that the workspace needs to be authored in? You are able to install multiple versions of Form (or Desktop) at the same time. You just need to specify a different install location for the other versions. 

Please let me know if you have any further questions. Cheers!

Hi Tandra.

I’m not trying to upload any workspace from 2024 to 2022. I know better than to even try it.

I’m just trying to use the FMEFlowJobSubmitter to run a job/workspace on our 2022 server from within the 2024 workspace. Or even the older FMEServerJobSubmitter copied from 2020/2022. And they all fail.

So unless - and this is my question - there have been some breaking change between 2022 and 2024 in how desktop/form communicates with server/flow, forward compatability shouldn’t be an issue.

So, have there been some breaking changes in this regard ?

Cheers.

Hi Lars, 

I understand the problem now, thank you for the clarification. I still don't think the FMEFlowJobSubmitter would work as the job submission request has likely changed from 2022 to 2024. 

A possible solution is to use the HTTPCaller like @redgeographics suggested. I asked our team and this was also the suggestion. 

Cheers, 

If this is true, it disappoints me a lot, I must say.

Newer FME desktop versions being able to access older FME server versions should be a success point of design IMHO. Server installations will typically not be updated as often as desktop versions, and not making this communication backward compatable will break work coherence.

In my case, luckily, I could get away with using a WorkspaceRunner, as I needed to have it running as a desktop scheduled task. Not optimal, but it works.

Cheers.

Hi Lars, 

I get the disappointment with older versions of server not working with newer versions of desktop, however when upgrading it is the best practice to upgrade both components at the same time and use the same versions for each. 

I’m glad you were able to find a suitable workaround for your issue. 

Kind regards, 

Hi @lifalin2016, 
I saw this post and just wanted to share in your disappointment and I get what you expressing. 

Between the FME versions mentioned we started moving to a new version of the API for FME Flow and hence likely the biggest reason things are not working from FME Form 2024 to the FME Server 2022.  As you know FME is complex product and it is challenging to keep all backwards compatibility happy.

The workflow you share is not common. But sure would have been nice for you!

As Tandra shared, we do recommend staying on similar major versions… but I understand that FME Server/Flow is not a straight forward upgrade, involving more testing effort, and longer duration to get onto the newer version.   That said, these days with security concerns of older software it is also important to be looking forward to the newer versions of FME Flow and is worth the effort in the long run to build this into the upgrade cycles of the FME Platform.