A space to discuss FME Flow
Recently active
I have a set of workspace apps on our Flow to convert data between file formats. After upgrading our installation in test, I experience some strange behaviour: While uploading data to convert, some files are accekted, while others are rejected. Looking into the network data using the developer tools, I find that the accepted files gives a response like this:{"serviceResponse": { "statusInfo": {"status": "success"}, "session": "3cc570c6-2d66-4d66-86af-22c6a2f56696", "files": { "path": "", "file": [ { "size": 1531, "name": "file name.kof" } ], "folder": [{"name": ""}] }}}The rejected files gives this response:<html> <head> <title>Request Rejected</title> </head> <body> The requested URL was rejected. Please consult with your administrator.<br> <br> Your support ID is: 12358467762813340<br> <br> <a href='javasc
We are upgrade to 2026.3.2 and it works until we change the FME Flow Core service to run on a local AD account. The full error is “There was an error submitting the job. COM.safe.fmeserver.api.FMEServerException: Could not get all queues due to connection issue to job router. Please try again.”I am looked in Task Manager processes and do not see a process called “redis-server”. I have tried restarting the services and rebooting the server.
I noticed in a recent update post that Safe are looking to implement a LTS release.I’m aware it’s still likely very early days, and a firm date for release will be difficult (impossible?) to share currently. It would be helpful to understand what the targeted timeframe is to help plan for future upgrades and implementations - is it a pre Christmas target? Or is it more likely to be a Q1/Q2 27?@stewartatsafe @rylanatsafe @steveatsafe
Hi all,I just checked and our Flow servers are running the vulnerable OpenJDK, has anyone heard any official notice from Safe about this? As I can see there are simple mitigations that one could enable, with arguments to the java process, but I am not sure of the implications for processing.https://www.cve.org/CVERecord?id=CVE-2026-114938https://calif.io/java4shellhttps://github.com/semgrep/detection-scripts/tree/main/CVE-2026-114938
While running a job on FME Flow 2024 Server, the following error occurred:"Unable to connect to the File Geodatabase located at '\vmbltstweu001\FS\TestFME\TestCheckout_ERW.gdb'. Please verify that the correct file path is specified and that the Geodatabase is not saved in a newer version of ArcGIS than the one installed on the server. The error code from ArcObjects is '-2147024891'."Could anyone please help me on that
For quite some HTTPcallers and different connections we switched the authentication method authentication from Basic (with username and password) to Web connections. When using Basic authentication, nu warnings or errors appear. But to keep the workspaces maintainable and safe, we decided to switch to Web connections.But after this change, the following warnings started appearing in FME Flow: HTTPCaller (HTTPFactory): Certificate verification will be disabled because verification is turned off for the '…' web connectionThe web connections have the checkbox for ‘Verify HTTPS certificates’ enabled (in Form).It happens for FME Flow web connections as well as HTTP web connection types.How can we avoid these warnings?We're using FME Form 2025.2.4 and FME Flow 2025.2.4
I am working with FME Flow 2025.2.4I have an automation with several Workspace Actions. Parameters are passed between the workspaces using JSON automation parameters.One of the Workspace Actions needs to be dynamic, so I pass the workspace name through a string automation parameter and the remaining parameters through a JSON automation parameter.Everything works correctly when I use only standard Workspace Actions. However, as soon as I replace one of them with a Dynamic Workspace Action, the JSON can no longer be parsed inside the workspace. It appears that FME Flow automatically deserializes the JSON parameter before it reaches the workspace.As a result, the value is no longer a valid JSON string, and transformers such as JSONExtractor or JSONFlattener fail when trying to parse it.For example, a parameter that arrives as:JSON{"umgebung": "tst","parameters": {"port": 54322}}is transformed into something like:Plain Text{ umgebung : tst, parameters : { port: 54322 } } which is no longer
When connecting FME Flow to Azure (Configuring Azure Active Directory with FME Server (safe.com) - the app needs permission to:Microsoft Graph > Application permissions > Group.Read.All, User.Read.AllMicrosoft Graph > Delegated permissions > User.Read However when using Azure AD and FME Form the following permissions are needed: Microsoft Graph User.Read Delegated Is it possible to limit the FME Flow permissions to be the same as FME Desktop - or is there a reason you also need Group.Read.All and User.Read.All ?
i’m using: FME Flow 2025.1.3.3 Build 25648 - win64I’ve configured the SMTP settings in System Email under Network and Email - it validates with a green checkmark.I then created a new flow with a Email - SMTP (received) using the same account as the one in system configuration. that also validates as correct.when i run the flow and send emails to the address, nothing triggers.i checked log files and found the following:FME automations log:Wed-14-Oct-2026 10:44:03.264 AM | INFORM | pool-6-thread-1 | SolarWinds Monitoring (85583c2d-4e61-4bd2-a384-41640a91ca35) | no-event | 410150 : (Automations) Logging events for component...Wed-14-Oct-2026 10:44:03.268 AM | INFORM | pool-6-thread-1 | SolarWinds Monitoring (85583c2d-4e61-4bd2-a384-41640a91ca35) | no-event | 410109 : (Automations) Creating link from trigger...Wed-14-Oct-2026 10:44:03.285 AM | INFORM | pool-6-thread-1 | SolarWinds Monitoring (85583c2d-4e61-4bd2-a384-41640a91ca35) | no-event | 410108 : (Automations) Creating email trigger..
Hi all!We are looking at patching up our two FME Flow 2025.2.1(Build 25815 - win64) instances according to the instructions given at https://support.safe.com/hc/en-us/articles/46792031942029-FME-November-2026-Security-UpdatesThe path we are taking is to apply the manual patching rather than upgrading at this time. Now we are a bit confused about the two parts of the fix that are needed - there is the Flow release hotfix, and there there is a file for Engine upgrade/installer.I the instructions under Option 2: Apply Manual Patch for FME Flow and Upgrade FME Engine(s) it says that both steps are are required for full remediation of the vulnerabilities....but then in the step-by-step instructions below it lists the Engine upgrade/installer as “Optional”. Is that correct, and if so are we leaving some vulnerabilities open… ?What also makes us hesitate a bit on the engine installer is that it has a later build number than we have in our Flow servers.It would be great if we could have this c
Hello Fme users, I have a question related to Fme Data Virtualization.When i create my Api documentation on swagger it works perfect untill i set security to Authenticated.Then i get error 401 , but i do not get Authorize button on my swager, i try creating token and everything from the documentation available online. But i cant get button authorize in any way.My enpoints are set to inherit Api Setting.I would like to ask for help
Not sure if it might benefit others but I’ve recently had to enable HSTS to harden the HTTP redirect from Port 80 to 443.Edited the web.xml file and located the HSTS Comments. (~Line 468)Added the below filters <!-- Enable HSTS --><filter> <filter-name>httpHeaderSecurity</filter-name> <filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class> <init-param> <param-name>hstsEnabled</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>hstsMaxAgeSeconds</param-name> <param-value>31536000</param-value> </init-param> <init-param> <param-name>hstsIncludeSubDomains</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>hstsPreload</param-name> <param-value>true<
Hi All, A couple of months ago, i made a post talking about making a transformer available for all users within a APP-V package. I managed making this with extra IT tooling, but in the mean time our new workplace is live and we are working with a newer concept. Now i we installed FME 2026.3.1.1 locally on our endpoints and we are seeing good results. However when trying to install a transformer from the hub, i am seeing following error message. ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'C:\\Users\\user\\AppData\\Local\\Temp\\pip-target-y7004105\\lib\\python\\fme_emailer-3.11.1.dist-info\\INSTALLER' Any reason why this is popping up?
Hi everyone, I have a workspace which exports a map as PDF using the featureWriter set on Adobe Geospatial PDF. When I run it in FME Workbench, my map looks exactly as it should (I have different parameters that set page size and orientation). For example, running it with the parameters Landscape, A4, returns exactly that. However, upon publishing on FLOW and running it there, I always get my page as Portrait, with a very small horizontal map on it. I pasted the examples below. I will also paste the settings of my FeatureWriter down below, in case I missed anything. I have made plenty of workspaces so far and I never had this issue before. Also, the pdf_page_pts field is getting populated everywhere, therefore I don’t think it’s a missing attributes kind of thing.I’m using FME(R) 2026.1.0.0 (20260311 - Build 26103.
About half a year go we set up a API Token thats being used by an external Web Application which triggers jobs on our FME Flow environment. This worked all fine till we upgraded to 2026.2 this summer.The right's we had set up were:Jobs AccessRecources Access (only to the required resources folder)Run Workspace AccessSince the upgrade to 2026.2 nothing was changed by us in these settings. The web application can still start jobs as needed. But any request of GET /jobs/{id} , /jobs/{id}/result en /jobs/{id}/log gives a 403 error now. The only way i found around it is to give the API Token the Jobs Manage permisson.But this feels wrong to me. If i read the documentation this would give the token access to all users jobs instead of only the ones started through this API Token. I can't find any mention about changes concerning this (only about the Tokens for FME Flow Apps which we are not using). Anybody has any idea what could be the cause here? Am i overlooking something?
I'd like to retrieve running job details using the API. I use GET /jobs/{id} for this. This works perfectly when I assign ‘all permissions’ to the API-token. But when I try to make the scope more specific by setting the access right to Jobs-->Access, I'm not able to see the job details anymore. What are the minimal rights to make this possible?I also assigned rights to a single repository and resource, but this is not visible on the screnshot.
@rahulsharma and I just troubleshoot FME Workbench not opening on a Windows 10 machine that has an NVIDIA graphics card. There were no warnings or anything when trying to get the program to open. The mouse would spin for a second and that was about it. After a lot of trial and error, we found that changing in the NVIDIA Control Panel from "High Performance" graphics to "Integrated graphics", FME opened right up without issue. Hope this helps! Make sure to add each application (even do it for the Help to actually open). If you know of a better way, I'm all ears.
FME Flow 2025.2.4.1I have set up an FME Workspace app to run a workspace. Additionally I have set up dynamic parameter configuration to data stream the parameters from a second workbench to be used in the app and first workbench. I have added two web connections (2 separate users) to Flow. I would like the dynamic parameter workbench to use the relevant web connection based on the user who runs the dynamic workspace and parse specific parameters back to the app and first workbench. Both users are set up in flow, and prompted to login in to the app, and I am then trying to pass the FME_SERVER_RUNTIME_USER variable to filter for the right web connection. However, if the 2nd user runs the app and grabs the dynamic parameters it is always the 1st user username value (the creator/owner) and therefore the incorrect web connection.Would anyone be able to offer any advice? How I can successfully get the runtime user of the dynamic param 2nd workspace?A separate resource file for each user migh
Hi all,i’m trying to add a FME flow automation that uses IMAP as a trigger, going through these instructions:https://support.safe.com/hc/en-us/articles/25407404506253-How-to-Connect-to-Microsoft-Exchange-Online-using-OAuth-2-0-Microsoft-Modern-Authentication#h_01HWPG1A9N334HV2CQHSS1092Ki’m not real clear about part 2 where it discusses setting up an emailer transformer - do i need to do that even if i am just trying to use FME Flow or is that for FME Form only? i’m kind of leaning towards only being for form, but we are trying to troubleshoot an issue so confirmation would be nice to have.
Hi everyone,I am facing an issue with FME Flow 2026.2 where an OpenAPICaller transformer is unable to fetch data from an internal service due to Kerberos authentication failing.Here are the details of our setup:.The Service: A "Data Virtualization" service hosted internally within our corporate network. The Environment: FME Flow is running locally/on-premise within the same corporate network (Local / Firmennetz). The Problem: The OpenAPICaller cannot authenticate via Kerberos, causing the data retrieval to fail.Has anyone successfully configured the OpenAPICaller (or underlying HTTP/web connections in FME Flow) to work with Kerberos authentication in a local network environment?Are there specific environment variables, or FME Flow service account permissions (e.g., SPN / Active Directory delegation) that we need to configure to make Kerberos pass-through work?Any help or workarounds would be greatly appreciated! Best regards,Michael
We need a FME Flow data stream which generates an HTML page showing an index of all available FME Flow Workspace Apps on our FME Flow instance.In FME Server 2022 REST API V3 we used [FME_Server_instance]/fmerest/v3/apps?.In FME Flow 2025 REST API V4, when we use the analogue [FME_Flow_instance]/fmeapiv4/flow-apps?, we do not obtain a result.Which is the appropriate call to obtain the information on all Workspace Apps available on an FME Flow instance in REST API V4 (as e.g. is [FME_Flow_instance]/fmeapiv4/repositories? to obtain all Repositories)?
It seems to me that the Map Configuration window doesn't work (or show) anymore when using the Geometry Picker in 'Full window mode'. I can also imagine that technically the window/menu does work/show, but is placed behind the 'full/expanded window' of the Geometry Picker, causing it not to be accessible/usable. To be clear. What I'm talking about is this menu/window, which does work when using the Geometry Picker in 'Inline mode';However, when I use the Geometry Picker in 'Full window mode', nothing seems to happen/show if I click on the Map Configuration button. E.g.;Are others also experiencing this issue? Is this a known bug? ps. I'm using FME Flow 2023.0.0.1 (b23288) on Linux.
I’m using a ChangeDetector to compare a field called ‘notes’ between a Viewer layer and a Collector layer. They basically have the same features, the Viewer layer is more of a catalog with some slight schema changes. The goal is to update the Viewer layer with any changes that are made to the Collector layer. I built the whole workspace in FME Form and tested it repeatedly with many features and everything worked as planned. I identified changes in the Collector layer and wrote them to the Viewer layer. Great.I go to publish the workspace to FME Flow and run it, and it fails the first time with the message:“ArcGIS Online Feature Service Writer: 'updateResults' error for a feature in 'my_layer'. The error code from the server was '1000' and the message was: 'Operation failed. The index entry of length 2256 bytes for the index 'notes_Index' exceeds the maximum length of 1700 bytes for nonclustered indexes.'” I finally discovered that a subset of features (about 3,691) from the Collector
Hi,I am wondering what is the best way to display messages to guest FME web app users? Similar to how the broadcast messages functionality works, but for users without a login. For background, my team has published several FME Flow workspace apps which are used by colleagues across our organisation. The users access the web apps without logging into FME Flow, so we don’t always know who all the active users are or their contact details.I am looking for the best way to display temporary information to these users within the apps themselves. For example, if downtime to our database is planned which will impact the FME app, how to display a message to the user. The best way I can think is using FME REST API to bulk update app descriptions with a message using PUT requests; and then repeat with a delete request to remove it later. However the formatting of the app descriptions is pretty limited for making a message stand out, and could be tricky to delete the temporary message without als
Hi there,I have installed FME Flow 2026.3 with HTTPS enabled in the wizard and completed the items that were missing from Configuring FME Flow for HTTPS: Using a PFX or P12 Certificate – FME Support CenterThis implementation didn’t work with an http 500 error.I started again with clean infrastructure with HTTP only and this worked. I ran the configureSSL.ps1 script and now it’s working with HTTPS which is great.Looking at Configuring FME Flow for HTTPS: Using a PFX or P12 Certificate – FME Support Center and comparing it to my configuration files and noticed configuration missing from the documented steps/part of steps. Does the configuration need to be updated with these missing configurations (eg. ws:// to wss://, turn off OpenSSL support using Tomcat native)? Thanks