FME Flow

Hi All, I’m sure this is very simple but I can’t seem to get it to work.I want to take the text body sent to my automation via a webhook and use it as the input to my workspace.So this would be the POST I’d then like to pass “this is not a test” into the workspace POST_test (below) so that I can process it further in the workspace. I imagine the issue is that I’m not defining where the information is coming from when entering the workspace, which is just a text file reader and text file writer for the purposes of this test.I followed this tutorial and can trigger the workspace using this method but I cannot get it to read the text direct

Hi FME’ers,Recently I wanted to set up FME Flow to receive notifications from a notification service. My initial thought was to use an Automation with a Webhook trigger. Unfortunately this didn't work, because I couldn't register the Webhook URL in the external notification service, because it resulted in a validation error. After further investigation, it turned out that the notification service was set up using the Guidelines for NL-GOV profile CloudEvents 1.0. In 3.1.3 Abuse protection it's indicated thatThe validation request uses the HTTP 

Has anyone got any tried and tested methods for testing ArcSDE connections that are stored in FME Flow, en masse rather than one by one.I thought i could use an SQL Executor but it appears FME doesn’t handle the error messages when they’ve come from a failed SDE connection so the workspace terminates if there is one bad connection.

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

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!I am using the Geometry Parameter to let the users draw their area of interest on FME Flow and then download the respective map. However, after publishing to FME Flow, I don’t see the map for the selection, nor am I able to turn it on in any way.I saw that usually there should be a map icon to the left of the text, which would open a map and let me draw a polygon of my AOI. What is the problem? I am using FME 2026.2.0.0 20260401 - Build 26291 and FME Flow 2026.1.1 Build 26121 (which should be compatible).  

We have an automation that is triggered daily with a CRON expression which runs 4 workspaces. The first 3 workspaces are run in parallel and the fourth runs on successful completion of one of the workspaces. Last night, two events appear to have been triggered at the scheduled time and so each workspace was run twice. Has anyone ever come across anything similar? I can’t see any obvious errors in the logs

We are running 4 FME Flow 2025.1.2 environments (DTAP) and 1 FME Flow 2025.1.3 lab environment, all in a fault-tolerant setup with 2 cores and 2 engine hosts.In our DTAP environments, we initially had an incorrect configuration:processmonitorcoreconfig contained localhost instead of FQDNs for both cores Each engine host was registered to a different core (processmonitorengineconfig)This resulted in jobs mostly being picked up by a single engine host, depending on which core was leading.In our lab environment, the setup is correct:FQDNs are used Both engine hosts are registered to a single core Fault tolerance works as expected (both engines process jobs, and failover between cores works correctly)We applied the same configuration changes to DTAP to match the lab setup. However, after registering both engine hosts to a single core, we observe the following

Hi,I’m using FME Flow 2025.2.4.I have an FME Flow Automation which runs 4 workspaces. Each workspace takes an email address parameter (which will be the same value for each workspace).I would like to use the same Automation to run on a bi-weekly schedule but also allow it to be run on demand via an Automation App, so I have 2 triggers: Schedule and Manual When the Automation is run on Schedule it should pass a pre-defined email address to the workspaces.When the Automation is run manually via the Automation App the user needs to be able to provide an email address at runtime.Is this possible? Or do I need to create 2 separate Automations?I know I can create a manual parameter that gets passed from the manual trigger to the downstream workspaces but if I configure the workspaces to use th

Hello FME community!I am using FME Flow 2025.2.4 Build 25835 - win64 and I am having issues with connections in apps and galleries. I have created Roles, shared my connections with full access, created new connections per this article http://fme.ly/zn8 nothing seems to work. The funny thing is that it has nt failed for me is I run the workspace directly in FME Server.Are there any tricks that I have not tired or is this a bug?Thank you in advanced for any help/ideas that you can provide. 

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 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 a

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’ve noticed a few issues since upgrading FME Form & Flow (FME Flow 2026.1 Build 26103 - win64) that seem to show up when I’m also developing in FME Form while remoted into our FME test VM.This is how I usually work, mainly because some jobs take a while to run and if I do them locally my PC can go to sleep after 5 minutes and the jobs fail. This setup has never had an issue in the past. Since the upgrade though, running Form this way can cause problems with FME Flow on the same VM. When I’m running heavier workbenches and CPU hits 100%, Flow can become unresponsive or look like it’s soft‑locked. This never happened before the upgrade.One thing I’ve noticed is that this seems to mostly affect SSO sessions. My theory is that when CPU is maxed out, Flow struggles to grab required info for SSO before it expires. Just a guess.

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