Introduction
Nested user parameters have been deprecated. When attempting to run a workspace in certain FME Flow deployments from 2023.2 onwards that contain a nested user parameter (i.e. one user parameter value is used within another), the job will not be submitted, and the user is met with the There was an error submitting the job message in the UI.
The following messages will appear in System Events and fmeserver.log, regardless of the source of the job:
Similar messages appear in action_workspace.log when ran from an Automation. If ran from a Schedule, no job will be submitted and no additional logs will be created.
FME Flow Parameters can still be referenced. These are not affected by this deprecation.
Workarounds
Two workarounds are available.
The first workaround is to create the User Parameter in an AttributeCreator or AttributeManager.
The second workaround is to make the User Parameter hidden. Hidden parameters' default value can reference other User Parameters without issue.