FME_SERVER_WEB_URL and FME_SERVER_HOST: 2024 vs. 2026

Regarding - Both values would be empty unless the workspace was actually running on FME Flow

Solution - Author can create choice user parameter…. local vs flow values. Utilise a ParameterFetcher followed by a Teste on this attribute. You’ll now have two data streams, one for workspace runner and the other for FlowJobSubmitter. Utilise a Logger to pass a message into the transaction log.

Bigger picture rather than using FME_SERVER_* parameters which only exists when executing on Flow… use the FME_JOB_ID flow parameter and you’ll get a similar outcome but have these pros:

• Only created when a job is submitted to Flow
• Set by Flow engine at runtime
• Not present in local runs

To understand the 2026 changes underneath FlowJobSubmitter due to the REST API v4 check out the documentation

Specifically the migrating tab… to understand how the Jobs endpoint has changed

Jobs

• Submit, monitor, and cancel jobs.

• Manage job queues and assign engines.

• Access job logs, statuses, and metrics.

all work with Job_ID 

My goto for checking whether the workspace is running on Form or Flow is a Tester with the criteria:

FME_JOB_ID > 0