FME Flow

Hi PeopleI have a bit of a weird scenario that has stumped our IT team and our FME consultants.Our setup is that we have FME Flow Hosted as the controller which passes the jobs to an on-premise FME Flow server.  Whenever the on-premise server is restarted (e.g. Windows patching) Flow Hosted loses the connection.While that is to be expected, the connection doesn’t come back on its own when the on-premise engines are back on-line, nor can it be restarted (it hangs on initialising).  The only way to reconnect the Hosted service to the Remote Engines is to complete drop the Remote Engine configuration and recreate it.Has anyone else come across this or, more hopefully, fixed it?Thanks

HelloWe have FME Server v2022.2.2 installed on Windows 2022 server and need to apply manual patch for security vulnerability, as per FME alert / articlehttps://support.safe.com/hc/en-us/articles/31265482270349-Security-Update-FME-Flow-Privilege-Escalation-Vulnerability#h_01JB2AENHZEBG9VCCFBJFTWX1RThe instructions include a note:*When moving/overwriting files, please ensure that the original permissions of the file being overwritten are preserved, this is ./opt/fmeflow.How best to do this?  We were planning on a simple copy and paste of the files themselves to the various directories, however this may overwrite existing permissions.  What method of copy & replace files is recommended, it would be helpful if the windows command or powershell script could be provided to assist Please adviseThanks 

Apparently since fixing this problem https://support.safe.com/hc/en-us/articles/25407612007949-Known-Issue-FME-Flow-Apache-Tomcat-Vulnerability-with-X-Frame-Options-headerIn FME Flow 2025.1, embedding FME Flow content to other pages is disabled entirely by default.  Is there any chance to allow embedding from known sources or is embedding considered so risky that this would not be even considered? 

We are working through the setup of a service user for a project, intended to only be able to create and run its own Data Virtualization APIs and nothing else.  The aim is to avoid excessive permissions. I have been searching for a list of recommended or minimum permissions but have not yet established that, so I’m putting the question out here.We have granted:Create/manage for data virtualization Run jobs Access Resources/DataWe’re looking into other permissions.We’ll work through it but I am definitely thinking that documentation of this would be handy from the Safe point of view to save time, if possible.  Possibly as an addition to https://support.safe.com/hc/en-us/articles/36098228739469-Secure-Data-Virtualization-Endpoints-with-Authentication 

As per this post last year, Salesforce is retiring the SOAP API login().  Any news from FME on when the Salesforce readers and writers will be updated?  

Hi everyone, I am having the strangest issue with FME Flow. I have a Form that process some data and then creates a pdf file. It works just fine locally with a UNC path. My issue is Flow, when I publish it, i get a permission denied, but the strange thing is it has no issue writing .txt file to that folder and to make it even more strange, it worked correctly two times out of the 50 tries I did changing things. I have even tried adding this UNC path as a resource in Flow and same result. Has anyone had such issues before? Any suggestions? 

I was checking through the list of possible job status for an asynchronous (Data Virtualization) workflow I have going and didn’t find a definition for ‘complete’, or a comparison of that value to ‘success’.  I was referring to the REST API V4 documentation here: https://support.safe.com/hc/en-us/articles/38420159907213-Submitting-a-Job-through-the-FME-Flow-REST-API-V4 Would someone with familiarity around those statuses be able to clarify the meaning of ‘complete’ and how it contrasts to ‘success.  AI relented from guessing and admitted it didn’t know. An update to this is that ‘complete’ is not listed in the OpenAPI spec for the FME Flow REST API V4, so at this stage is the documentation incorrect?https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json "status": { "type": "string", "description": "The current status of this job", "enum": [ "queued", "running", "success", "failure",

I have a workflow that reads an Excel file (attached image ExistingSourceDataset_XLSXR_image.png) then uses an AttributeManager transformer to modify the data, then writes the results to a SQL server database (attached image sampleFMWimage.png). Works great.I’ve been asked if it is possible to replace the hard coded Excel filename in the ExcelReader with a prompt for the filename. I thought it would be easy. I was wrong. My original thought was create a User Parameter (I’ll call it excelFilename) and then replace the existing source dataset with that User Parameter. Found no way to do that. Has anyone done something similar? Or know how to make that work?

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?

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?

I have automations owned by ‘admin’ (superuser).If I come with another user that has full access, stop the automation make changes, save and enable again…. I find the next scheduled run under the Job logs, it is then run under the username that last edited it.this can lead to issues if the dependent components like run workspace > connections etc are also not granted permissions to that userI’m using 2026,1 … was this always the case or does the owner of the automation run the job? Maybe this change in the FME REST api v4 ? 

Hi,I noticed something unexpected today with deployment parameters that I would like to hear others opinion on.The situation at hand is that we have several automations running on FME Flow. In these automations an external action is present to send an email upon success. For the 'Email_To’ parameter of this email action, a deployment parameter is being used.It thus currently looks something like this;And then in an automation it would look like this;Then I had this automation running, and if it gets triggered, the email is send like intended.But now I wanted to remove one recipient of the emails. Therefore, I changed the value of the deployment parameter email_to from 'email_adress_1,email_address_2’ to 'email_adress_1’;Now for the unexpected behaviour. I noticed that after changing the value of the email_to deployment parameter, if I would again manually trigger the (still running) automation, I noticed the email would still be send to both the email adresses, where I expected it to h

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

I have an automation that runs every 15 minutes on a single engine with a ‘repeat on interval’ schedule trigger. Usually, it takes less than 10 minutes but sometimes it can take more than 15 minutes and once a week on mode overwrite it takes about 25 minutes. If one of the workspaces of the automation is still in progress, is there a way to skip the trigger for the next automation?

I want to create custom UI for a flow app like create button. I want to build some sort of app that gave user more creative UI and good experience whether it is by HTML or CSS.

Hi Folks,Almost weekend and we got a bit of a strange situation. We have a Flow App that is being used by most of our users. They upload a GeoJSON and select if they want Aerial Imagery or Topographic Background. The result is a generated PDF Map.This process works fine for all but one user. When this user uploads a GeoJSON we see in the log the following error:90 2026-8-7 15:44:02 | GEOJSON Reader: The file 'C:\ProgramData\Safe Software\FMEFlow\resources\system\temp\upload\[Projectname]\[Workspacename]\auth-user\[USERNAME]\508a819f-ee99-bb88-9785-82b3a169082e\[GeoJSONname]' does not exist91 2026-8-7 15:44:02 | An error has occurred. Check the logfile above for detailsIf any other user uses the same GeoJSON file the process works fine.We checked the following:User rights are identical The GeoJSON is valid (others can use it fine) We checked the timestamps in the DataUpload log with the Job Log and the file is uploaded before it's read. We checked with the user where it doesnt work if t

Hello!We are using Flow FME 2026.1.2. I would like an overview of when most automations trigger. Unfortunately, there isn't much information about it in the documentation, so I did some research and found this post:I tried it and now I'm experiencing some really strange behaviour. Until today, I could run all the API requests I ever needed and get results. I can even run FMEURL/fmeapiv4/schedules?limit=100&offset. What I can’t run is the solution in the thread:FMEURL/fmeapiv4/schedules?limit=100&offset=0&sourceType=automationAs soon as I add 'sourceType' as a parameter, I get the following result:{"message":"Unauthorized request by user USERNAME due to lack of proper permissions or the object does not exist."} Do I need special privileges to use this parameter? Or is it just bugged? Is there a workaround to achieve my goal of creating an overview of automation schedules? Many thanks in advance for your help.Kind regards, Henning

Hi there,We are updating our connections to ArcGIS Online through FME Flow to use OAuth as much as possible.I have created an OAuth Web Connection and Web Service for each of the ArcGIS Online orgs we want to connect to from Flow.My question is, if we need to connect to one of these orgs with multiple users, do we need a different specific web connection for each user pointing at the same web service?Thanks,Marc

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. 

I have an FME Flow 2026.1.1 Automation that runs a series of FME Form workspaces. The 1st workspace grabs data from an AGOL Hosted Feature Service. This automation runs every 30 days. But, every time it runs it gives me an AGOL re-authorization error. Then I need to go into the FME Form workspace and sign back into AGOL and republish to FME Flow. What is the best way to keep signed into AGOL for more than 30 days using FME? is there something I need to do in FME Flow, if so, what? I am the admin of our AGOL account. I know I can use a token, but are these good for more than 30 days or just 2 weeks? It would be nice if could stay signed in a year or longer that way the automation would run without the AGOL re-authorization error. 

Since upgrading from FME Flow 2025.2 to 2026.2, we are seeing a recurring authentication problem with our Workspace Apps. When a user opens or reloads an app, a native browser Basic Authentication popup appears intermittently, roughly every second or third load. Because we use SAML, our users have no local username or password to enter and are forced to click Cancel every time. After cancelling, the app works normally, but the repeated prompt is disruptive for end users.Our setup: FME Flow runs under HTTP behind an IIS reverse proxy (Application Request Routing) that enforces HTTPS. Authentication is handled through SAML with Azure AD as the identity provider using SP initiated login. On IIS, only Anonymous Authentication is enabled while Windows and Basic Authentication are disabled, and the SAML base URL is correctly configured.Using the browser developer tools, I captured the exact request that returns the 401. It is a GET to the Data Upload Service that the app fires in the backgro

Quick question; if I want to use a token to authenticate my Data Virtualization, rather than a FME Flow user, I need to build it myself, correct? (and then do that for all endpoints of course)

Like the title says, whenever I try to publish a workspace with a sharepoint connector webservice to fme flow, I get below message. I have no problem writing to the same repository if I don't have sharepoint connector webservice in my workspace. Moreover I have no problem using the sharepoint connector webservice local on my fme form. Does anyone might have ideas why I get this error when trying to publish the sharepoint connector webservice to fme flow? 

Has anyone tested the workaround described here?Workaround for geometry parameter basemap bug | CommunityIt’s changed the basemap against the workspace, and it shows the changed basemap during app creation but when you go to the app itself it shows the original default basemap.