FME Flow

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:- Source  Choose between:  - Current FME Flow, analyze the logs of the system the workspace is running on    - Archive, upload a ZIP file containing logs from another FME Flow instance- Logs Archive  Enabled only when Source = Archive. Allows uploading the ZIP file containing the logs you want to investigate.- Start Date and Time  A date/time pa

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): Processed 16,927 of 16,927 features FME Form:ArcGISOnlineConnector: Updating file cont

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 = exportFolder + ".zip"# from zipfile import ZipFile# for file in ZipFile(zipExportFolder).namelist():# archive previous zipdestZip = os.path.

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 ends unexpectedly.Relevant log snippet:Tue-07-Apr-2026 04:31:29.648 PM INFORM requesthandler 401831 : Accepted new client connection from /127.0.0.1 on port 7500Tue-07-Apr-2026 04:32:14.937 PM INFORM Thread-46 localhost_Engine1 WARNING: sun.reflect.Reflection.

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 workarounds but it is annoying and I am wondering if it is a bug or a no

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 workspace while the other uses the updated version? Has anyone seen this behavior before?

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 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….We configured different things to get it work, first of all we added the server certificate (of the server to which we are trying to connect with the HTTPCaller) to the Java keystore, as described in: SSL Certificate Handling for FME Transformers – FME Support Centerkeytool -import -trustcacerts -keystore "G:\FMEServer\Utilities\jre\lib\security\cacerts" -storepass changeit -noprompt -alias aseqltst100Root -file "<location file>"And:key

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 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", "timeFinished": 1774908390000, "timeQueued": 1774908385000, "timeStarted": 1774908385000, "outputLoca

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

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): Cloned 0 input feature(s) into 0 output feature(s)REGLE_TOPOLOGIE KO_SURFACIQUE_OVERLAPS_SURFACIQUE Outp

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\fmepython312\Lib\site-packages)Previously, we used FME Flow 2024.1.2.1, which used python 3.12, FME Flow now uses python 3.13 and as the module is installed in

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.