Skip to main content
Question

Deployment Parameters and WorkspaceRunner

  • April 1, 2026
  • 3 replies
  • 96 views
ca
Contributor
Forum|alt.badge.img+3
  • caContributor
  • Contributor

I have a parent workspace and that is calling a child workspace in FME Form using a WorkspaceRunner transformer. The child workspace references deployment parameters.

 

When the child workspace is run from the WorkspaceRunner I receive the following error:

 

ERROR : 2: Undefined macro `APP_API_URL' dereferenced in file.

 

APP_API_URL is the name of a deployment parameter that I have permission granted.

 

I tried creating a published parameter in the child workspace whose default value is the deployment parameter but I get the same result.

 

Are deployment parameters not supported with WorkspaceRunner?

 

FME(R) 2025.2.0.0 (20251120 - Build 25810 - WIN64)

    3 replies

    david_r
    Celebrity
    • david_rCelebrity
    • April 2, 2026

    You should not use the WorkspaceRunner on FME Flow, it’s not supported. From the manual:

    Use the FMEFlowJobSubmitter in stead.

      ca
      Contributor
      Forum|alt.badge.img+3
      • caContributor
      • Author
      • Contributor
      • April 2, 2026

      Sorry I wasn’t clear, the workspaces are being run from FME Form, not FME Flow. We are using the deployment parameters for standardization and access control.

      crystalwang
      Safer
      Forum|alt.badge.img+21

      Hi ​@ca,

      Thank you for posting your question on the FME Community, and apologies for the delay in response.

      Unfortunately, deployment parameters are not supported in child workspaces run via WorkspaceRunner and this is a known design limitation. Workspaces referencing deployment parameters must be run from either FME Flow (via the REST API or GUI) or directly from FME Workbench.

      If deployment parameters being supported for child workspaces run via WorkspaceRunner is something you’re interested in, I encourage you to click this link and submit an idea capturing your product suggestion and use case. Other FME Community users can upvote ideas, and our product team reviews them for future inclusion in FME.

      Community Stats

      32,569
      Posts
      123,643
      Replies
      40,857
      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.