Automation

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

If an automation is triggered by a schedule, you can obtain the schedule properties via the Schedules list.  https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/schedules/list If an automation is triggered by a topic, how do you obtain the name(s) of the topic(s) that trigger that automation?If an automation posts to a topic, how do you obtain the name(s) of the topic(s) that automation posts to?

It seems the issue described in the related topic, where the job variables show in the result, instead of the values, has never been resolved. Or the issue has returned in version 2025.2.4.As a workaround I can send an email to a Teams-channel. But I looks a lot better when I send an adaptive card to the channel, using a Workflow in that channel.But as described in the related topic, when I send a adaptive card with a HTTP Request in an Automation, a job variable like {automation.name} just shows as {automation.name} in the result. Of course I would like it to show the name of the automation.Is there a way to make this work? Or is this a bug and I just have to wait when it will be fixed?

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

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 = exp

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 workar

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

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

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

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 

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

Hi FME community,I am trying to fanout to a GDB using FME 2025.1.2 in windows.   I keep getting this error :Esri Geodatabase Writer: Feature Type Definition 'd_y_n' was requested, but not defined. Please visit https://www.safe.com/supportGEODATABASE_FILE writer: An error has occurred. Check the logfile above for details When i just simply export without fanout it works fine. I have tried removing fme_template_feature_type using attributemanager (even though it is not an attribute in my database) also tried AttributeKeeper.  Nothing seems to work. Thank you   

I have an automation that trigger an HTTP Request to get informations on a job :host.com/fmeapiv4/jobs/{user.id} The HTTP request is send and I get my response : {"id":122,"engineHost":"localhost","engineName":"localhost_Engine1",... ,"elapsedTime":29176,"cpuTime":7687,"cpuPercent":26.346997532218264,"peakMemoryUsage":186314752,"lineCount":2439,"warningCount":27,"errorCount":0,"remoteEngineName":"","remoteEngineJobLogUrl":""}I would like to send an other http request based on the content of the body response :host.com/fmeapiv4/accounts/{runtimeUserID} The runtimeUserID key is a key in the http.body attribute which is a JSON value.I cannot extract some portions of this JSONI have try to get other keygs but it always failed :{http.body

I create a simple FME Flow App - the user enters a word to search content. The FME workspace put the results into a html file under Resources/Data. I want put a link to this html file on the Flow App page to allow the user to click the link and open the html file in the browser to see the content. Can this be done?

Hi all,I am struggling to get the following to work. In my IT environment we use APP-v to deploy FME workbench. Now I want to automate the license within the package. So I installed FME workbench but is automatically opens the licensing manager, which is nice but I want to specify the license myself. What file can I make that I can implement in the application so it instantly recognizes its license. I tried the admin guide but did not work. We have floating licenses.So what file can I make to specify the license within the application, so that users don't have to enter it themselves. 

When setting up an automation trigger using Amazon SQS I get the above error. Is this something anyone has seen before? It might be our firewall. We do use a proxy server that has had certificate issues before. Sometimes we have to ignore SSL warnings.

I have FME Automations that use the “FME Flow Schedule”.  In the “FME Flow Schedule”, I am using the Schedule Type “CRON Expression”.  Is there a way to get a report for all the “FME Flow Schedule” from all the FME Automation so that I can know when an FME Automation is scheduled to run?

Currently doing some testing after upgrading FMEFlow to 2025.2.1It appears that the validate button on the JMS trigger now just returns an ‘Invalid Parameter’ message Previously it produced something slightly more descriptive.i.e. Failed to find JMS object / Realm is currently not reachableIs a more detailed message available in a log somewhere, if so where should i look? I have it all set up and working correctly in 2025.2.1, this is just for future reference.

Hello,  So I have a platform that utilizes Fire Hose API for their data stream. My stream will have thousands of changes a second. I need to connect to this stream, clean/filter the data, and have the data end up showing on an ArcGIS webmap. What would the path be? I am not exactly sure how I connect the firehose stream to FME (I have flow and form). My thought process is Connect Firehose to FME (not sure how, not HTTPCaller right?) → Create data stream to process data → connect stream to GeoEvent Server → Display on Webmap? Is my thought process accurate? Any help is appreciated!

Is there any way possible to send an HTTP Response after receiving a webhook trigger in FME Flow Hosted Automations? I am attempting to set up an automation that runs in response to webhooks coming from Monday.com, however before I can start configuring the actual webhooks, monday.com requires verification that I have control of the endpoint. I need to do this by having the platform send a JSON challenge to the endpoint URL, which must then be responded to with an identical JSON POST body. I believe it must also be returned with a status of 200. Documentation on setting up monday.com webhooks here. I have tried to accomplish this by adding a workspace after the webhook trigger to pull the IP address that the challenge request was sent from from the HTTP headers, an