Deployment

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

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

I recently come across some workspaces that I can't seem to upload anymore to FME Flow (2024.2). I already found the culprit, but still would like to understand why this happens and how to fix it permanently.Publishing a workspace gives an error. Dragging it into FME Flow will give a screen and that will get stuck and dragging multiple workspaces at once will upload all of them except the one not working and also not giving any feedback that one has not been uploaded. Eventually I found that pressing the Edit button behind the Job submitter gives more options and that there is something red. Easily to miss…So settings this to empty or another one gives me the ability to upload again. But next time it is again on the red one. Why does it keep remembering a FeatureReader that is not in the workspace again. I found also some documentation about what the use is of this feature, but I'm not sure I completely understand. If somebody could explain in a few sentences that would be great.

Hi,Looking through updating our workflows to accomodate for the new v4 API Endpoints and getting the error message “Content type 'application/octet-stream' not supported” when testing out the new POST /repositories/{repository}/items/upload Is the content-type application/octet-stream no longer supported as part of these API updates and if so any suggestion for the alternate content-type to use when uploading .fmw files Thanks 

Every night we run make backup of the FME FLow (2025.2.2) system configuration. Since a couple of days this results in an error: | An error occurred: Topic SYSTEMEVENT_ERROR_LOG does not exist..No backup is created. When trying to start the backup manually, the result is the same Does anybody have an idea of what may cause this?

Hi there,If we change the URL of our FME instance all the redirect URIs of our OAuth web services will be pointing to the old URL.Is there a way to bulk update them, either through a setting or an API call? Thanks,Marc

Hello,We are still seeing an issue in our FME Flow 2025.1.2 fault-tolerant setup. In a previous forum post, we were able to solve part of the problem: FME Flow fault-tolerant setup: jobs stuck in queue after correcting engine/core configuration | Community. However, jobs still occasionally get stuck in the queue.When this happens, we inspect the database and see that some values appear to be overwritten again. In the fme_core_node table, the router_queue_nodename and job_queue_nodename fields for one of the Core (not leading one) instances are changed, and that Core’s own FQDN is written there. In fme_publisher_node, the “wrong” node is marked as leader = true — meaning a different leader than the one shown in fme_core_node. In some cases, we also see a different leader marked as true in fme_queue_node, although not always.Restarting the Core(s) usually resolves the issue temporarily. After a restart, the expected values are present in the database again, jobs are picked up normally, a

I’m trying to update FME Flow from version 2023.1 to 2024.2. Upgrading In Place, On the Same Machine.I want to use the encryption key from the previous FME Flow installation so I could restore the previous configuration in the new installation. This means I also want to update my FME Flow Database password in fmeDatabaseConfig.txt.Before starting the newly installed FME Flow, the encryptConfigSetting.sh script works and outputs the password in the format of DB_PASSWORD=fme_enc:xxx.After I’ve started the FME Flow, the script does not work anymore:Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/codec/digest/DigestUtils        at COM.safe.fmeserver.encryption.FMEEncryptionKeyFileUtils.computeChecksum(FMEEncryptionKeyFileUtils.java:22)        at COM.safe.fmeserver.encryption.FMEEncryptionKeyAccessorFile.calculateChecksum(FMEEncryptionKeyAccessorFile.java:86)        at COM.safe.fmeserver.encryption.FMEEncryptionKeyAccessorFile.loadKeys(FMEEncryptionKeyAccessorF

HI there,I have a FME Flow 2026.1 deployment in a fault tolerant configuration with ALB and SSL enabled in AWS.The HTTPS traffic on port 443 to the ALB is working fine going to core and running jobs on the engines.I’m struggling in finding the documentation on the ALB setup for the websocket and setting the ‘Internal WebSocket URL’ in the system configuration section in the WebUI so I can use notifications/topics in my automations as triggers.I’m basically looking for ALB configuration. So, my questions are:Does the ALB require port 7078 listener and then to target the EC2 on port 7078?Which EC2 should be in the target group? is it core or engine?What would be the health check url to the EC2 to determine the EC2 can receive the websocket traffic?What url would you set for the ‘Internal WebSocket URL’ in the config settings based on above?At the moment, I have looked at safe github repo for AWS IaC which is very generic and the ALB fails on the health check to the core EC2 If someone co

For automations run at different frequencies e.g. hourly, daily, monthly, how to manage logfiles cleanup to best use of space?Is it possible to set the hourly automations logfiles clean up daily, while daily automation log files clean up biweekly. 

I was looking to upgrade FME Flow 2024 to FME Flow 2026 and ended up getting an impassable situation. I was following this process, which I’ve done in previous upgrades (ie. to version 2024):https://docs.safe.com/fme/html/FME-Flow/AdminGuide/Upgrade-in-Place-Same-Machine.htm - I am stuck after step #4. Here are my specific steps:Uninstall FME Flow 2024 from Add or Remove Programs Run FME Flow 2026.1.1, using Express install Open http://<host>/fmeserver/ -> “ERR_CONNECTION_REFUSED”From fmeserver.log: INFORM   main   401970 : FME Flow is not licensed for this machine. For assistance, contact sales@safe.com or your local Safe Software reseller. (-1) INFORM   main   401972 : Total number of available engines is 0 INFORM   main   401961 : Licensing Manager init FAILED INFORM   requesthandler   401831 : Accepted new engine connection from /127.0.0.1 on port 7070 INFORM   fme-engine-registration-1   401937 : Accepted new FME Engine connection. INFORM   fme-engine-r

Is it possible to turn off log entries like these?Workspace was last saved in FME version: FME 2025.1.3.1 (20251021 - Build 25645 - WIN64) Failed to free sufficient memory to reach the process usage limit. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applicationsThese just add clutter to the job reviewing process.   

We are implementing a CI/CD pipeline for FME Flow using an Azure YAML pipeline. When exporting an FME project from DEV with deployment parameters enabled under Advanced Options, those parameters overwrite the values in ACC and PRD during deployment. If the same project is imported manually, this issue does not occur.Is this a known bug in the FME Flow API? Or is there a recommended way to prevent deployment parameters from being overwritten during automated deployments?Additional details:If all advanced options are manually unchecked, deployments work as expected. The token used for the pipeline requires full permissions (fmesuperuser); otherwise, roles cannot be deployed. Restricting permissions or deployment parameter rights results in nothing being deployed.FME Flow version we have is 2024.1.2Any insights or best practices would be appreciated!

Has anyone else run into issues with how things are displayed in FME Flow 2025.2.1 Examples: Engine Assignment Rules - we have two hosts which differ in name by suffix only. The way engines are displayed on the Engine Assignment Rules tab means you can’t quickly tell which engines are assigned as the critical bit is displayed as … (the full names are available on mouseover) The hostnames displayed in No proxy also have their urls partially replaced with …. so there appears to be no way to actually check via the user interface what values are entered here. In 2024.1 these values were displayed in full 

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

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?

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.

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,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.  

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

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?