FME Flow

Hi, I am a software developer, but don’t know much about FME yet. Please forgive my ignorance :-)I was asked to create a simple wrapper around the REST API v4 that lets a user start a job, and download the results as a zip file.Generating a token, submitting a job, and getting the job’s status is fairly straightforward, but I am at a loss when it comes to downloading the results. I see that there is another API /fmedatadownload, but it seems that the token I use when submitting the job does not work here. I tried passing it in the Authorization header, as a query parameter, and I also tried Basic authentication, but all of these return HTTP 401I am sure this must be very simple, but I am probably overlooking the obvious here.

Hi all,I have a fault tolerant deployment of FME Flow 2026.1 in our private AWS account. Our security team requires us to limit the number of ports to be opened between WebUI/Core and Engine hosts (eg. least privilege).Is there a best practice rule/formula in calculating the number of ports required to be opened depending on the number of engines per host and the number of hosts in your deployment and the starting port number? ThanksExample:3 engines / host and 2 hosts = 6 enginesIs there a redundant factor that needs to be applied? eg. 2 timesTherefore 3 engines x 2 hosts x 2 redundant factor = 12 TCP ports are required.The starting port number should be from 50000 fmeFlowConfig.txtFME_SERVER_PORT_POOL=50000-50011

Hello,FME Flow requires ArcGIS Server to allow for direct access to geodatabases and ArcGIS Server is licensed per 4 physical cores.As such, if you have an FME Flow deployment machine with 8 physical cores, will this mean 2 ArcGIS Server licenses?From and Esri perspective, I would say yes (I work for Esri Australia) but wondering if Safe Software know of any arrangement, given that ArcGIS Server does none of the processing, just providing the libraries.Mark

Hi there,I have installed FME Flow 2026.1 and have used the HTTPS option with a pfx certificate from the installer wizard on Windows Server 2022 AWS EC2.I can open the WebUI with https:// and everything looks fine and log in with SSO/SAML. The ‘Services’ page has the urls as https:// as well. Question: Is the steps in ‘Configuring for HTTPS’ still required?

 Using $ref in FME Flow Data Virtualization APIs for Deduplication This might be an imprecise post, but my question is whether FME Data Virtualization follows the exported API specification or the visual editor’s interpretation - and why. I need guidance on restructuring my specifications: Data Virtualization seems to accept arrays of schema references but silently drops them, replacing them with blank references in properties but losing the json-type array in endpoint responses.This inconsistent handling of $ref makes it unclear how Data Virtualization processes schema references — especially for arrays, since the visual editor only supports $ref for objects. Thanks for taking the time in advance!EDIT: Im am currently using FME 2025.2.4 Build 25835 The Use Case of Arrays with $refHere is an example usage of Arrays of Referenced Objects from the OpenAPI s

Hello community,for a few days, I have been struggling with our FME Flow. It occasionally throwsand I am the admin, I asked myself and… crickets.The only change we did recently is a Python library install.FME Flow gets in this error communicating state and then recovers. We tried restarting FME Flow, it likely made some difference (I am not sure whether it indeed fixed the problem even for a short period of time as FME Flow works between these messages anyway), but it didn’t last.This is FME Flow 2024.0 build 24612.Any ideas will be much appreciated.Thank you :)

I have installed FME Core on windows machine and distributed engine on Linux machine. I am getting following error in my logs “ERROR : FME Engine failed to register with FME Flow 'FME-CORE-DEV' on port 7070. Failed to verify message authenticity” Engine appears on FME FLOW but it is not active and always appers as disconnected.

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

Hello Everyone, I have an FME Flow 2025.2.4 automation that contains nineteen individual FME Form 2025.2.4  jobs. In addition to those nineteen jobs, I have two separate FME Form jobs that are used only for email notifications. One notification job is intended to run when jobs succeed, and the other is intended to run when jobs fail. Both of these notification jobs contain an FME Form 2025.2.4 Emailer transformer in their build. All nineteen FME jobs in my automation are connected to the Success notification job through their success ports, and those same nineteen FME jobs are connected to the Failure notification job through their failure ports. This wiring ensures that the appropriate notification workflow is triggered depending on the outcome of each job. The goal is not to send an email for every individual job result. Instead, the goal is to send a single consolidated email per outcome type of Succeed and/or Failure. For example, if nin

I utilise Deployment Parameters to sde database connections. When upgrading to 26.1 and then starting to test, deployment parameters failed due to being missing. I moved the shared resource path between versions, so I guess this is to be expected2026-4-21 16:25:07 | An error occurred while attempting to retrieve the connection parameters from the connection file 'D:/FMEFlowShare/resources/system//_RTIOSDE_TEST_DEVDATA_FME_Flow.sde'Deployment parameters, specially SDE file connections….are not restored from application backup, when you change the Flow Shared Resources from the C:\ProgramData\Safe Softwareto a D:\FMEFlowShare 

Hi all, I have a workspace that was running fine on server, but now the user is unable to upload an input file as a temporary resource. The upload says completed but the OK button is greyed out. This seems to be the case with all workspaces, not just the one in question. Any ideas whats going on? Thanks,  Owen 

Hi,I need to make the Esri Arcgis connector available for all users within a APP-V packages, however these connectors install under the app data folder. Is there any way to install these connectors on a program files or data folder so that all the users can make usage of the Hub connectors. Is there a way to change this path? Thanks in advance. I already tried to copy the files to the program data however FME doesn't see the files and is unable to access the connectors. Yours sincerely.  

After upgrading from FME Flow 2024.2.3 to 2025.2.4, the labels (titles) under Gallery Apps are now rendered as blue, underlined hyperlinks.Previously, the labels were displayed as plain black text without underline, even though the entire app tile was clickable.2025.2.4:2024.2.3:Are there any built-in configuration options or recommended approaches to control the styling of Gallery App labels? We are aware that other organizations have experienced the same issue after upgrading from the same versions.

Hey everyone! I wanted to share something I’ve been working on for a while.When I’m debugging our own FME Flow, or one from a supported user, I often need to dig into the log files to track down errors or evidence of what went wrong. This can be really time-consuming: there are many files to open, and some of them are very large. Most of the time I end up just jumping between files and scrolling to the right timestamp, instead of actually focusing on what happened. To make this easier, I built an FME workspace called FMEFlowLogInvestigator.This workspace can be published on FME Flow with the Data Streaming Service. It takes four user parameters:

If an automation is triggered by a schedule, you can obtain the schedule properties via the Schedules list.  https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/schedules/list If an automation is triggered by a topic, how do you obtain the name(s) of the topic(s) that trigger that automation?If an automation posts to a topic, how do you obtain the name(s) of the topic(s) that automation posts to?

Can the dynamic parameters in FME Flow Apps, as described here:Dynamic Parameter Configurations in FME Flow Apps – FME Support Centerbe made to cascade, i.e. so the value chosen in one parameter affects the choices available in another?How does one structure the JSON to do this?

Hi, I have a problem with runing Flow Apps on Flow 2026.1When i press run i got : And in F12 tab shows Internal server error 500 Job Section is empty, i dont even get faild or cancelled job.Any idea what could it be?My Form and Flow version are both the same, 2026.1 Thank you in advanced! 

Hi all, we are on Flow 2025.2 and we use Geometry Parameter for quite a few ws apps. Now we are living with the bug FMEFLOW-26285Changes to the default basemap of a geometry user parameter under the Parameter Defaults when creating/editing a Workspace app do not get applied to the Workspace app. Users accessing the workspace app will see that the default basemap is unchanged. Any tips for a workaround? Can one change the default using javascript in the webpage possibly?

Hey all, After updating my FME Form to version 2025.2.2 & updating the ArcGISConnector package one of my FME Flows has stopped operating in the same way. I have an ArcGISOnlineConnector Transformer which updates a hosted CSV item on an ESRI Enterprise system. This had been previously working well & updating each row within the CSV and the CSV on Enterprise showing as updated after the flow had completed. Following the update the Flow now only updates the First & Last feature according to the log. The CSV on the Enterprise does also not show as having been updated when the flow has completed. This worfklow does still work on FME Form. Previously FME Flow went through each feature on by one like the second setFME Flow:125 2026-4-17 08:52:50 | ArcGISOnlineConnector_2_CALLER (PythonFactory): Processed 1 of 16,927 features126 2026-4-17 08:52:51 | ArcGISOnlineConnector_2_CALLER (PythonFactory): Processe

I have several automated jobs that use either a startup or shutdown python script.  These scripts run fine in workbench and even in the ESRI Python interpreter on the Flow machine.  The issue arises when I run them from Flow.  When it gets to the script it will output expected products until the exportToPDF command at which point it fails.  No errors are indicated anywhere except in the Engine Log where this is displayed: WARN     localhost_Engine2   393562 : Process "localhost_Engine2" ended unexpectedly. Being restarted on attempt 1…Example of script:import arcpy, os, sys, time, shutilfrom datetime import datetimesdpFolder = r"****OBSCURED****"exportFolder = os.path.join(sdpFolder, "SiteDevPlanFiles")date = time.strftime("%Y-%m-%d")dateFolder = os.path.join(exportFolder, date) archiveFolder = os.path.join(sdpFolder, "_Archive")zipExportFolder = exp

Most REST API’s I have worked with work in a similar way with regards to authorization: Based on some credentials, you generate a token, and use that token for subsequent requests. You can usually create as many tokens as you want using the same request. What I noticed in FME (but please correct me if I’m wrong), is that a token must have a unique name, and when using the same request, you get a response that says Specified user token already exists. Of course I can update an existing token, or delete it and create a new one, but that means that in most cases, I need two requests instead of one.Another thing I noticed is that expired tokens are not deleted automatically: A request to /fmeapiv4/tokens showed me a token that apparently I generated 7 years ago! I am curious about the reasoning behind this way of using tokens. I mean, why does a token have to have a name, and why would you keep generated tokens forever?

Hello everyone,We are encountering an issue with FME Flow 2025.2.1 where jobs stop unexpectedly without any error message.Scope / Versions✅ Issue occurs in: FME Flow 2025.2.1 ❌ Issue does NOT occur in: FME Flow 2024.1.2.1 FME Form 2025.2.1 This suggests the problem is specific to FME Flow 2025.2.1 and not related to the workspace or FME Form itself.Observed behaviorThe job stops abruptly without any error reported in the FME Flow UI or job log. Enabling Debug logging in FME does not provide any additional insights. The same workspace runs successfully in: FME Form 2025.2.1 FME Flow 2024.1.2.1 FME Flow loggingWe reviewed additional server-side logs.In fmeprocessmonitorengine.log, we consistently see that the engine en

I started protecting my workspaces with passwords because they sometimes contain sensitive informations (like embedded connections) and I noticed a weird issue when I uploaded them on FME Flow 2024.2.5.I use the parameter FME_MF_NAME in different places, for naming different outputs. As soon I added the password, the workspaces started to fail. Notably I have one workflow which requires launching multiple workspaces sequentially, the main one launching the others with FMEFlowJobSubmitter. All the protected workspaces have their FME_MF_NAME overwrited by the FME Flow. All the logs show the same message upstream, something like this:FME Configuration: FME_MF_NAME is 'wb-tmpXXXX'Which is weird because the parameter of the workspace is correctly set with a message like this:`--FME_MF_NAME' `myworkspacename.fmw'Using the parameter FME_MF_NAME during the job gives 'wb-tmpXXXX' instead of ‘myworkspacename.fmw'.I can find workar

Hello,I believe I’ve encountered a bug in FME Flow 2023 and would like to know if others have experienced something similar.I recently updated a workspace by changing the recipients in an email transformer and overwriting the file on FME Flow. This workspace is triggered by two separate schedules: one for Mondays and one for Thursdays. Both schedules are identical except for the day they run.Surprisingly, when the Thursday schedule ran, the email was sent to the old recipients (prior to the update). However, when the Monday schedule ran, it correctly used the updated recipients.I have verified the following:The logs confirm that both schedules are calling the exact same workspace file in C:\FMEFlowShare\repositories. I manually checked the workspace on the server, and the parameters are definitely correct.Why would one schedule seemingly use a cached or "ghost" version of the

In Flow 2025.1 the message user parameter type would show with an info icon and blue background in a workspace app.  In 2026.1 there is no colour behind the message, just the text and the plain white background.  I cannot show much here but this is what I’m seeing - the top line should have the blue background and info icon:Interestingly in the workspace app editor the blue background does show for messages there.