FME Flow

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.  

For one of the first versions of Data Virtualization, it is required to create a work-around for IIS. Unfortunately it is not possible to react on the knowledge article directly anymore.I just updated to build 25835 and after a quick test I see the work-around is still required. From which version onwards is this not necessary any more?

Dear FME users,Already for days we're trying to get an automation to work with a HTTPCaller using certificates.The HTTPcaller works when we put in the HTTPCaller the option 'Verify HTTPS Certificates' to 'No’, see printscreen below.However when we publish the workbench to FME Flow and run it from an automation we are getting the following two errors:Aanroep_gateway_lijst_ftp (HTTPFactory): [1]: HTTP transfer error: Problem with the local SSL certificateAanroep_gateway_lijst_ftp (HTTPFactory): An error occurred while accessing the URL 'https://tst….

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

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. 

Dear All starting using FME Flow - MCP Server,I have an existing FME workspace performing semantic search using Microsoft Copilot Retrieval API searching against SharePoint Document Library, which was used with a FME Flow App (Semantic Document Search Engine). It will return HTML based search results with generative AI vibe-coded UI. It has been working quite well for our end users.Now, since we are all very excited about potentials of FME Flow - MCP Server. I have made a copy of my workspace and convert the out to JSON writer or TEXT writer to streaming JSON of the semantic search results.However, Claude AI seems to only be able to get returns of job submission log from the MCP tool: { "id": 182, "featureOutputCount": 2, "requesterHost": "X.X.X.X", "requesterResultPort": 57366, "resultDatasetDownloadUrl": null, "status": "SUCCESS", "statusMessage": "Translation Successful",

Hi,I am using FME 2026.1, trying to create a map using AttributeCreator+ PDFStyler.However, when I set my label height to for example, Arial,5, my text comes out bold. When I select Arial,5,BOLD, my text comes back looking regular. Is that a bug just for me? I was stuck on it for ages trying to figure it out. Yes, it is also the case when i set a font size like 5 (not from an attribute).I am wondering if anyone else has this issue.   

Testing after upgrading preprod to FME 2025.2.1 and it appears that an issue that would previously (FME Flow 2024.1) be reported back from the database, i.e. incorrect user/incorrect syntax do not appear in the log filee.g. running a workspace with an SQLExecutor with a query with incorrect syntax in FME Form 2025.2.1 results in an error, e.g.“java.sql.SQLException: Line 1: Incorrect syntax near '}'.”No such message appears when running the workspace in FME Flow. The workspace fails but no SQLException is returnedThis appears to be the same whether you connect with using JDBC or Microsoft SQL Server (JDBC). 

The Black line starting from left should align(shown in yellow) with red line.how to accomplish this in fme.Polygon 1 and 2 belongs to one layer and polygon 3 is from another layer. 

If you have an existing automation and need to make a change, you make your changes and publish \\ overwrite in FME Forms. Once you go to the automation and stop it, all parameters are reset to defaults. This happens even to workspaces that were not updated. This has happened the last 2 or 3 releases, currently we are onFME Flow 2023.1Build 23619 - win64

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?

I’ve tried reviewing results from /schedules. This doesn’t seem to include our schedule triggers in automations.Neither /automations or /automations/{id} return the required information.Can anyone point me in the right direction?Thanks!AW 

Hi all!In our 2025.2 Flow installation we have AD synchronization and authentication for quite sometime, with some 100+ users and a number of groups. Now we are about to deploy SAML - I am able to get it to work for a new user/role, but if there is an existing user/role there is a collision, and the process fails.Am I understanding it correctly that I actually have to delete (or at least rename) all users and roles before we can start using SAML fully?What we see in the logs:417551 : An error occurred during SAML login: Specified user role already exists.417551 : An error occurred during SAML login: Non SAML user account "nordpil" already exists. Please contact system administrator for support. 

Hello,I have a workspace with a custom transformer that does lot’s of things but we can consider this :Get a list of feature type to read Read data with a feature writer Make a bunch of tests with spatial relators, feature merge and plenty of transformers If some error are found : those objects are outputed If no error are found, nothing is outputed.In local, with FME Form, no problem, it works, nothing is returned :REGLE_TOPOLOGIE KO_PONCTUEL_TOUCHES_LINEAIRE Output Renamer/Nuker (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)REGLE_TOPOLOGIE KO_PONCTUEL_INTERSECTS_PONCTUEL Output Renamer/Nuker (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)REGLE_TOPOLOGIE KO_LINEAIRE_INTERSECTS_LINEAIRE Output Renamer/Nuker (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)REGLE_TOPOLOGIE KO_LINEAIRE_CROSSES_LINEAIRE Output Renamer/Nuker (TeeFactory):

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 :)

Hello there FME community! I am working as an external consult with the GIS-team at a company where I have a shared responsibility of the FME environment. We are managing about 200 workspaces, each running more or less every day on Flow moving data around and generating reports.Every second year we upgrade the FME instances, setting up new virtual machines for FME Form, installing new FME Flow instances and upgrading all the workspaces. This takes a long time, as we have to open all workspaces, save them in the new version and then test that they behave like before. While this works for us and the customer is pleased, I really believe that the process could be more efficient. Are you in a similar situation? How are you approaching the upgrade? Are you upgrading the FME environment in a similar way, or do you have a more efficient approach?  Best regards,Jacques de Flon

Has anyone ever encountered this system event message previously?Event Description: Triggered whenever an error message is logged to fmeserver.log.Event Title: Error Message LoggedMessage: Parameter macro error for job requestThis is occurring when a workspace in an automation completes successfully and should be triggering a downstream workspace but instead this message appears in the system events and no workspace is triggered. The parameters in the workspace that is failing to be triggered are not dynamic and have not changed recently. Since the automation has been switched on it has run successfully 139 times but we’ve now seen these messages in 5 of the past 6 runs. FME Flow 2024.1

HelloWe have just updated FME Flow to 2025.2.4. As we also need the qfieldcloud-sdk module, I installed it with pip-install "C:\Program Files\FMEFlow\Server\fme\fmepython313\python.exe" -m pip install qfieldcloud-sdkSomehow this installation got mixed up and the module was installed in python 3.12"C:\Program Files\FMEFlow\Server\fme\fmepython313\python.exe" -m pip show qfieldcloud-sdkName: qfieldcloud-sdkVersion: 0.13.0Summary: The official QFieldCloud SDK and CLI.Home-page: https://github.com/opengisch/qfieldcloud-sdk-pythonAuthor:Author-email: Ivan Ivanov <ivan@opengis.ch>License:Location: C:\Program Files\FMEFlow\Server\fme\fmepython312\Lib\site-packagesRequires: certifi, charset-normalizer, click, idna, pathvalidate, requests, requests-toolbelt, tqdm, urllib3Required-by:(» Location: C:\Program Files\FMEFlow\Server\fme\

Hello,I am trying to run a workspace using FMEFlowJobSubmitter to our FME Flow server, but the job submission fails.The log shows the following error:This workflow was working with our previous installation using FME Flow 2023, but since our new installation the job submission fails.Does anyone know what could cause this error?Thank you.

Hi FME community,I am trying to fanout to a GDB using FME 2025.1.2 in windows.   I keep getting this error :Esri Geodatabase Writer: Feature Type Definition 'd_y_n' was requested, but not defined. Please visit https://www.safe.com/supportGEODATABASE_FILE writer: An error has occurred. Check the logfile above for details When i just simply export without fanout it works fine. I have tried removing fme_template_feature_type using attributemanager (even though it is not an attribute in my database) also tried AttributeKeeper.  Nothing seems to work. Thank you   

Hello Forum, In FME Flow's App builder I would like the word in the OK button to be 'Run' instead of 'OK'. This is because OK, is often thought of as also meaning close (yes, I know the users could just close the browser tab).  But of course, in the case of FME Flow Apps OK most definitely means 'run it'. So, it would be better if the word OK was replaced by Run.  I've looked in Flow Apps>Manage Workspace Apps>(click the App in question)>Customise, but there doesn't seem to be an option to change the wording of the OK button. Any ideas? Thanks,Stuart 

Hi have a flow which takes in data from a secure file transfer protocol, processes the data and produces two CSV files.  Currently these files are written to a local drive.  How can they be saved to the FME server so that they can be used in other workflows during a particular session and then deleted afterward?  Im guessing a flow parameter needs to be created and then pointed to by the writer but I really cant figure this out exactly

I have an automation that trigger an HTTP Request to get informations on a job :host.com/fmeapiv4/jobs/{user.id} The HTTP request is send and I get my response : {"id":122,"engineHost":"localhost","engineName":"localhost_Engine1",... ,"elapsedTime":29176,"cpuTime":7687,"cpuPercent":26.346997532218264,"peakMemoryUsage":186314752,"lineCount":2439,"warningCount":27,"errorCount":0,"remoteEngineName":"","remoteEngineJobLogUrl":""}I would like to send an other http request based on the content of the body response :host.com/fmeapiv4/accounts/{runtimeUserID} The runtimeUserID key is a key in the http.body attribute which is a JSON value.I cannot extract some portions of this JSONI have try to get other keygs but it always failed :{http.body

I am logging in  FME FLOW on our local FME Server (v25.2.1) using my AD Credentials that I manually enter.  When I get logged in, I try to open several workbenches that I had previously uploaded and to which I had full access. However, I get a popup message “Unauthorized request by user (myaccountname) due to lack of proper permissions or the object does not exist.”I contacted the local FME administrator who advised that my account had full permissions to the workbenches I was trying to access.  He advised I log off and back in several times, the implication that he was reviewing or changing something on his end.  And always the same resulting error message.The administrator is adamant that I should be able to access the workbenches, however, I cannot.I had asked that the issue be escalated but the administrator was unsure where to escalate the issue.I am looking for any advice on the issue.Thanks in advance

As I understand things, currently one can only use the Esri enterprise geodatabase formats on a Windows host. When moving to kubernetes it is then needed to use queue control to direct those jobs to Windows VMs, which is not ideal.When can we expect those drivers to also work on Linux? And is the problem on the Esri side or the Safe Software side?