Skip to main content
Question

FMEFlowJobSubmitter: Item parameter retrieval failed (Not Authorized)

  • April 22, 2026
  • 2 replies
  • 20 views
lenabagh
Contributor
Forum|alt.badge.img+3

Hello Community,

I am struggling with FMEFlowJobSubmitter transformer in FME 2026 and am leaning on the community to help me figure the problem out.

I have a workspace that runs a child workspace using WorkspaceRunner locally or FMEFlowJobSubmitter on FME Flow. It worked perfectly well on FME 2024.1. Recently, we upgraded to 2026.1 and the workspace started failing on FME Flow. It looks like the workspace fails to run the child workspace.

Now, when I open my main workspace with 2026.1 FME Form and get to FMEFlowJobSubmitter parameters, I get an error message in the log:

This is the whole experience:

What I’ve checked/done so far:

  • Both, FMEFlowJobSubmitter from 2024 and FMEFlowJobSubmitter from 2026, throw the same error in 2026 FME Form.
  • I am fmesuperuser and fmeadmin, i.e. my privileges are quite extensive.
  • Users were restored from backup after FME Flow upgrade, so technically there should be no changes in access privileges
  • I checked Items and didn’t find anything that would feel related to the problem.

Any ideas and suggestions will be very much appreciated.

Thank you :)

2 replies

ecx
Supporter
Forum|alt.badge.img+6
  • ecxSupporter
  • Supporter
  • April 23, 2026

A few thoughts


With the connection you’re using (solidworkflow lb), have you re-authed it since the upgrade? Has this connection worked in other workbenches since the upgrade? Make sure this is working would be my first step. 


“The FMEFlowJobSubmitter submits jobs via the FME Flow REST API and does not make use of the transformation services.” source
Transitioning from fme 2024 → 2026 means that FME api v3 (used in 2024) has changed to fme api v4, this may have had an impact. 

lenabagh
Contributor
Forum|alt.badge.img+3
  • lenabaghContributor
  • Author
  • Contributor
  • April 23, 2026

​@ecx yes, the connection works as I was able to e.g. publish the updated workspaces using it.

API should not be part of this problem… I think. Even if API is used as FMEFlowJobSubmitter backend, I upgraded FMEFlowJobSubmitter, so it should be fully compatible with 2026

It seems to be something with permissions, likely with permission to do something with the child workspace, but I don’t understand what it can be.

Community Stats

32,502
Posts
123,432
Replies
40,696
Members
Terms & ConditionsCookie settingsAccessibility 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.