Introduction
When working with FME, encountering unexpected behaviors or limitations can be frustrating. To help navigate these challenges, this article provides a comprehensive list of known issues affecting all currently supported versions of FME.
Each issue includes details on its impact, available workarounds, and whether a fix has been implemented. Our goal is to ensure transparency and provide solutions wherever possible, so you can keep your workflows running smoothly.
If you encounter an issue not listed in this article or have any questions about a known issue, please contact the Safe Software Support team.
Known Issues in FME 2023.0 to FME 2026.x
For a list of issues for retired versions of FME, see Known Issues in Retired Versions of FME.
| Feature | Product | Description | Workaround | Affects | Status |
|---|---|---|---|---|---|
| Emailer Transformer | FME Form | When the Emailer transformer from package 3.11.0 is configured with Generic SMTP, the workspace fails with a timeout error. This is caused by a malformed connection string containing a trailing |
Manually set a valid value for the Timeout parameter in the transformer settings. Or downgrade the Emailer package to version 3.10.0 and re-add the transformer to the canvas |
2026.2 | Workaround |
| Schedules & Automations | FME Flow |
Opening an existing Schedule or Automation with a Schedule Trigger can incorrectly reset the Start Date to current time minus 24 hours. Hence, saving or rerunning the Schedule/Automation overwrites the original scheduled time. FMEFLOW-27887 |
Use CRON Expression type instead |
2026.1 2025.2.4
|
Workaround |
| Python and ArcGIS Pro 3.6 | FME Form |
FME 2025.1, 2025.1.0.1, and 2025.1.1 are incompatible with the release version of ArcGIS Pro 3.6 when user Python is used in the workspace. FMEENGINE-86435 |
Upgrade FME Form. See Known Issue - Workspace error when FME 2025.1.X are used in combination with the ArcGIS Pro 3.6 for more details | 2025.1.x | Resolved 2025.2 |
| Jobs | FME Flow | FME Flow shows a job has failed, but it is still running on a distributed engine host FMEFLOW-26336 |
Please see the Known Issue article for instructions |
2026.x 2025.x 2024.x 2023.x |
Unresolved |
| Backup & Restore | FME Flow |
An error may occur when attempting to create a backup for an FME Flow instance that utilizes SQL Server or Oracle for the system database FMEFLOW-25997 |
There are two options to resolve this. Please see Known Issue: "Invalid column name 'connectiontype'" During FME Flow Backup for instructions |
2026.x 2025.x 2024.x 2023.x |
Unresolved |
| Esri ArcGIS Feature Service Reader/Writer; FeatureReader/FeatureWriter | FME Form |
Writing to a Feature Service with UNIX epoch millisecond values, errors may occur FMEENGINE-87880 |
For details on the errors and the workaround please see Known Issue: UNIX Epoch Milliseconds Date (Datetime) Handling by Esri ArcGIS Feature Service Format |
2024.x |
Resolved 2026.1 |
| FME Hub packages and RHEL9 | FME Form |
FME Hub packages are not able to install on RHEL9 with error:
FMEENGINE-92113 |
Install the Seahorse application and create a password keyring item named See Known Issue: RHEL Failing to Install FME Hub Packages for instructions |
2026.1 | Workaround |
| Dynamic Parameters in FME Flow Apps | FME Flow |
Flow App's with a Dynamic Parameter Configuration with a workspace data source will fail to load the JSON schema. When using the Test function, an error will appear saying either of the following:
FMEFLOW-27717 |
In the schema workspace, edit the JSON writer output path to only the file name (example.json) and republish the workspace. | 2026.1 | Workaround |
| Oracle Reader / Oracle SQLCreator ORACLE_DATABASE |
FME Form |
Oracle query that returns the warning:
Users will see the ORA-24347 message, features are rejected, and the translation terminates after the warning. |
None |
2025.2.2 2025.2.1 2025.2 |
Resolved 2025.2.3 |
| Dashboards | FME Flow |
The workspace JobHistoryStatisticsGathering (in the Dashboards repository) fails with a 422 error when over 1000 jobs have been completed in the past 24 hours. FMEFLOW-27332 |
Contact Support for an updated version of the workspace. |
2026.1 2025.2 2025.1 |
Workaround |
| MultipleGeometryFilter, MultipleGeometryCoercer and all transformers with GQuery GML |
FME Form |
GML readers in FME 2025.2 and newer read multiple geometries as a generic aggregate rather than a specialized multiple-geometry aggregate. This change affects workflows that rely on MultipleGeometry transformers, across all GML-based formats (including GML, CityGML, INSPIRE, and AIXM 5). FMEENGINE-89391 |
For more information please see Known Issue: MultipleGeometryFilter, MultipleGeometryCoercer and all Transformers with GQuery Not Reading Multiple Geometries in FME 2025.2 | 2025.2 |
Resolved 2025.2.4 |
| Feature type fanout only writes out first group of features ACAD, GEODATABASE_FILE, OGCGEOPACKAGE, SHAPEFILE |
FME Form |
Problem is known to affect SHAPEFILE, GEODATABASE_FILE, FILEGDB, OGCGEOPACKAGE, and ACAD writers. FMEENGINE-87496 |
None |
2025.1.2 2025.1.1 2025.1.0 |
Resolved 2025.1.3.3 |
| Dataset fan-out broken GEODATABASE_FILE, OGCGEOPACKAGE, SHAPEFILE |
FME Form |
Related to FMEENGINE-87496, problem is known to affect SHAPEFILE, OGCGEOPACKAGE, and FILEGDB. FMEENGINE-88226 |
None | 2025.1 |
Resolved 2025.2.0.0 |
| Annotations | FME Form |
Workbench crashes when modifying annotations using More Text Formatting Options. FMEFORM-34340 |
None | 2025.1.0 |
Resolved 2025.1.1 |
| Backup and Restore | FME Flow |
If a backup file contains two workspaces in the same Repository which differ only in capitalization (such as example.fmw and EXAMPLE.fmw), the import will fail. Errors include:
|
Before creating the backup, remove the naming conflict by deleting a workspace. It can be reuploaded with a different name. Contact support if you have already uninstalled the previous instance of FME Flow. |
2026.x 2025.2 2025.1 |
Workaround |
| Jobs | FME Flow |
When customizing the columns on the Jobs page, any changes made are not reflected in the actual display FMEFLOW-27127 |
Clicking "Restore Defaults" can allow for customization, however the Ran By column will be removed |
2026.1 2025.2 |
Unresolved |
| Automations | FME Flow | When using REST API V4 endpoints with the HTTP Request Action in the automation, the HTTP request fails and the following error message shows Failed action due to error: Permission denied: connect
|
Use the HTTPCaller transformer in FME Form for REST API V4 endpoints. | 2025.1 |
Resolved 2025.2 |
| HTTPS Configuration/Silent Installs | FME Flow |
When performing a silent install with with propert the PFX certificate is not from the propert
<FMEFlowDir>\FMEFlow\Utilities\tomcat\conf\certs FMEFLOW-26994 |
Run the configureSSL.ps1 script after installation. See Configuring FME Flow for HTTPS |
2026.1 2025.2 |
Workaround |
| FME Flow Backup / Upgrades | FME Flow |
During the backup process it fails with the error message:
FMEFLOW-26009 |
Identify any automations using a System Event trigger and temporarily change the trigger (for example, to a manual trigger). Perform the backup and restore, then switch the trigger back to System Event. |
2025.x |
Resolved 2026.1 |
| FME Flow Web Connection | FME Flow |
Got the FMEFLOW-26942 |
Delete the FME Flow web service from Flow UI, and then upload a new Web Connection on FME Form from the same version of FME Flow. |
2026.x 2025.x |
Workaround |
| AutodeskDocsConnector (safe.autodesk-docs) ACAD |
FME Form |
Web connection fails to authenticate using the embedded browser, showing an “unsupported browser” and/or a Redirect URI or Request error and preventing sign‑in. FMEENGINE-88785
|
If on 2025.2, use the external browser authentication Proxy Redirect Strategy. If on 2025.1.3.1 or newer, change the User Agent to System Default in the web service definition. |
2025.0.x 2024.x 2023.x
|
Workaround |
| FME Flow Authentication Services | FME Flow | Updating Windows AD - SSO Service Account Password in the FME Flow Web UI does not update DB value, leading to login failure because it is reading the old password value. FMEFLOW-26930 |
Make a REST API call to update the password Or, update the password field in the database: dbo.fme_ldap_server_property.SsoPassword Note: Because the password in DB is stored in encrypted form, create a second Windows AD connection with the correct password and copy its encrypted value into the original connection. |
2025.1 2025.0 2024.x |
Resolved 2025.2 |
| FME Flow Web Connection |
FME Flow FME Form |
In FME Form when trying to connect to Flow with SAML, instead of redirecting to the authentication page, it redirects to the Flow machine UI FMEFLOW-26420 |
Restart FME Form and retry Flow SAML web connection login | 2025.2 |
Resolved 2026.1 |
| FeatureWriter format Microsoft SharePoint Online List SHAREPOINT |
FME Form |
Automatic attribute definition from the User Attributes tab may result in incorrect attribute type assignment. FMEFORM-34568 |
Use manual attribute definition Use the Microsoft SharePoint Online List writer directly |
2025.1.x 2025.0 2024.2 2024.1 |
Resolved 2025.2 |
| Engines | FME Flow | If FME Flow is installed on an unsupported OS (e.g. Windows Server 2016), engines will fail to start or show in the UI | Upgrade the OS to a supported OS, or downgrade FME Flow. | 2025.x | Workaround |
| Remote Engines | FME Flow | After updating a database or web connection, a job submitted to a remote engine still runs with the old connection values. FMEFLOW-26733 |
Reset the remote engine cache under Engine Management > Remote Engines Services > Actions. Resubmit the job using the connection. |
2026.x 2025.x |
Unresolved |
| Web Connections | FME Form | Google OAuth2.0 Authorization Code web connections return the error "Malformed auth code" on authorization in FME Form. FME Flow is not affected. FMEENGINE-88450 |
Use a non-affected version of FME Form before or after 2025.1.3. | 2025.1.3 |
Resolved 2025.2 |
|
ArcGIS Feature Service Writer
|
FME Form |
The ArcGIS Feature Service Writer fails to insert multipart geometries into an existing Feature Service with the following error message:
This error is caused by ArcGIS Online not accepting polygons with more than 1 boundary. |
If you need to work with true curve data, the recommended workaround is to upsert your data or overwrite the feature service, as required by current Esri behavior. As of v3.19.1 of the Esri ArcGIS Connector, the default setting for Use True Curves will be set to No Or, use the older ArcGIS Online Feature Service Writer. |
2025.x | Workaround |
| Snowflake FeatureWriter SNOWFLAKE |
FME Form |
Snowflake FeatureWriter does not respect the Use Bulk Mode parameter, even when Use Bulk Mode is set to Yes. FMEENGINE-87666 |
Open the FeatureWriter and set the Use Bulk Mode parameter to No. Click OK to accept the new parameters. Re-open the FeatureWriter parameters and set Use Bulk Mode to Yes. Click OK. The FeatureWriter should now use Bulk Mode when inserting records. |
2026.x 2025.x |
Workaround |
| Backup and Restore | FME Flow |
Restore fails with the error message FMEFLOW-25989 |
Inspect the restore log to determine which Schedule caused the bug (this will be the last item processed). Open the schedule, remove the password parameter's default value, re-attempt the restore, and reinstate the value of the parameter in the new instance. You may have to repeat this process multiple times if there are multiple Schedules/Parameters. Contact support if you have already uninstalled the previous instance of FME Flow. |
2025.1 |
Resolved 2025.2 |
| ArcGIS SDE Geodatabase and File Geodatabase GEODATABASE_SDE, FILEGDB |
FME Form FME Flow | New data types, like "Big integer", introduced in ArcGIS 3.2 cannot be written to the geodatabase, even though Esri version dependencies are met. There is a message in the log saying FME used a different data type. | For FME Form, use ArcGIS Pro as the client software instead of ArcGIS Server. For FME Flow, upgrade to 2025 or use a different data type. For more information, see ArcGIS Data Type Changed After Writing to Esri Enterprise Geodatabase (ArcSDE) |
2024.x |
Resolved 2025.0 |
| FME Flow Web Connection | FME Form |
Users without access to Deployment Parameters are unable to connect to FME Flow, and the following error message is shown FMEFORM-33648 |
Grant user access to Deployment Parameters, or grant access to Version Control and upload workspace directly to Flow UI in Repositories. |
2025.1 2025.0 2024.2 |
Resolved 2025.2 |
| Workspace App | FME Flow |
Changes 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. FMEFLOW-26285 |
Users will have to manually update the Basemap URL after opening the Workspace app via Map Configurations |
2026.x 2025.x |
Unresolved |
| Data Virtualization | FME Flow | The Data Virtualization API endpoint request URL is not updated to the resolved web URL in the Swagger UI. The issue was caused by a mismatch in the FME_SERVER_WEB_URL setting between fmeFlowWebApplicationConfig.txt and fmeFlowConfig.txt. |
Run a text editor as an administrator and open fmeFlowWebApplicationConfig.txt, located at <FMEFlowDir>\Server\. Change the FME_SERVER_WEB_URL value to the one used in the fmeFlowConfig.txt. Save the file and restart the FME Flow Application Server service. |
2025.x | Workaround |
| Schedules | FME Flow | The Schedules page shows a schedule has a Deleted Workspace, but the workspace exists and continues to run on schedule. This can occur if a schedule's workspace is removed from FME Flow and the re-uploaded or re-published. FMEFLOW-24775 |
Open the affected schedule, reselect the repository and workspace, and save the schedule. |
2026.x 2025.x 2024.x 2023.x |
Unplanned |
| FME Flow Apps |
FME Flow | When a workspace that contains the DocumentPDF writer is selected during workspace app creation (regardless of whether it's enabled or disabled), no services will be listed and the app cannot be created (this workspace will work fine elsewhere). | Remove the DocumentPDF writer completely and use the FeatureWriter set to DocumentPDF | 2025.0.1 |
Resolved 2025.1 |
| Database Connections | FME Flow |
When a database connection is created with an connection file using a Resource Connection that points to a remote file location, workspaces that use the database connection will fail on FME Flow with the error: FMEFLOW-24925 |
Add the connection file using the full UNC file path via the ‘Enter URL/Path’ option or store connection file in FME_SHAREDRESOURCE_DATA folder |
2025.x 2024.x 2023.x |
Workaround |
| Users and Roles | FME Flow | Users with full permission to repositories could not access those repositories from FME Flow UI and get the error message "Unauthorized request by user xxx due to lack of proper permissions or the object does not exist". |
Give users Version Control (Access) permission and then log in to FME Flow again to access repositories they have permission to. |
2026.1 2025.2 2025.1 2025.0 |
Workaround |
| Web Connections | FME Flow | When a proxy is configured with basic auth, and the password contains a forward slash (/), jobs with transformers that connect to web services like ArcGIS Online or SharePoint fail with the error 'Failed to parse' |
Do not use a forward slash (/) in the proxy password, or add the web service's URLs to the 'No proxy for' list in FME Flow. Please see FME Flow proxy documentation for more info. |
2025.1 2025.0 2024.x 2023.x 2022.x |
Resolved 2025.2 |
| User Parameter | FME Flow |
Table User Parameters are not displayed correctly in FME Flow, and are difficult to edit. FMEFLOW-25837 |
Make sure table User Parameters are unpublished, if used at all. See Known Issue: Table User Parameters Displayed Incorrectly in FME Flow |
2025.1 |
Resolved 2025.2 |
| User Parameter | FME Flow |
Extra quotation marks around published user parameters choice configuration values in FME Flow. Running the workspace in Flow results in no features being written. FMEFLOW-25712 |
Use StringReplacer transformer to remove quotation marks from attributes |
2025.x 2024.2.1 |
Resolved 2026.1 |
| Data Virtualization | FME Flow |
Data Virtualization API docs don't load when an IIS/ARR Reverse Proxy is used. When trying to load the docs, the error "No API definition provided" is shown, as is a yellow "INVALID" button. FMEFLOW-25714 |
See Known Issue: Data Virtualization API docs don't load with IIS Reverse Proxy | 2025.1 |
Resolved 2025.2 |
| Data Virtualization | FME Form |
In the Data Virtualization reader, the source_path attribute is set incorrectly when run in FME Form. The attribute value is either "." or missing. FMEFLOW-25943 FMEFORM-34563 |
See Known Issue: source_path set incorrectly in FME Form |
2026.x 2025.2 2025.1 |
Workaround |
| MSWord Reader SAFE.MSWORD.MSWORD |
FME Form |
Not all features are read in, and the data cache is not created. Running the workspace produces the following error:
FMEENGINE-87355 |
None at the moment |
2025.0 2024.2 |
Resolved 2025.1 |
|
SQL Server Writer Azure SQL Server Writer |
FME Form FME Flow |
When writing non-spatial data to SQL Server / Azure SQL Server with a FeatureWriter, the workspace fails with the following message: "The default spatial column name and type were not specified." FMEENGINE-87346 |
Use a regular SQL Server / Azure SQL Server Writer instead of the FeatureWriter. | 2025.1 |
Resolved 2025.1.0.1 |
| FME Flow Web Connection | FME Flow FME Form |
FME Flow web connection doesn't work when connecting from FME Form. Users may experience failed translations with the following translation log in FME Form error messages: or Unable to retrieve public key From Flow. Unable to establish secure communication with Flow. Deployment parameter access failed (Connection Error) - Unable to connect to FME Flow
|
Restart FME Form |
2025.1 2025.0 |
Resolved 2025.2 |
| Jobs | FME Flow |
Data Download service: files are missing from the .zip file output, but when the same job is run against the Job Submitter service, the files are output. FMEFLOW-23081 |
Make sure the data set paths for writers or Feature Writers registered with the Data Download Service do not include a combination of $(FME_SHAREDRESOURCE_DATA) and an attribute. This, along with publishing the workspace with the FME_SHAREDRESOURCE_DATA parameter set, will lead to an invalid .zip path where data cannot be written. Example of a dataset path that will cause this issue: $(FME_SHAREDRESOURCE_DATA)\filename (@Value(attribute)).txt |
2026.x 2025.x 2024.x 2023.x 2022.x |
Unplanned |
| Version Control | FME Flow |
History is not visible for some .fmw files or repositories when using the FME Flow UI. This is caused by spaces or international characters in .fmw file names or repository names. FMEFLOW-25125 |
You should still be able to view history from the http[s]://<your FME Flow URL>/fmeserver/repositories page, however, only the first time that the page loads. Reload the page to view history again in the same session. | 2025.0 |
Resolved 2025.1 |
| User Parameters | FME Form |
Invalid parameter warning appears if a value in a compound visibility test condition for a Conditional Visibility parameter contains spaces or special characters but the parameter is otherwise valid. FMEFORM-32997 |
Omit spaces and special characters from any compound visibility's test condition for Conditional Visibility parameter. | 2025.0 |
Resolved 2025.1 |
| WFS and FeatureReader WFS |
FME Form | Error when using WFS with FeatureReader "No geometry mapping entry found for 'fme_point' in metafile 'C:\Program Files\FME 2025.1\metafile\WFS.fmf'." FMEENGINE-86597 |
Using the standard WFS Reader rather than a FeatureReader will work as expected. | 2025.0 |
Resolved 2025.1 |
| Backup and Restore | FME Flow | After upgrading, no subscriptions are displayed, and there is an Internal Server Error message. FMEFLOW-25422 |
Upgrading to FME Flow 2024.2+ resolves some of the issues that cause this problem. If not, please submit a ticket to support for assistance. Also see: FMEFLOW-23758 |
2026.1 2025.x 2024.x |
Unresolved |
| Publishing to FME Flow | FME Form |
Error when republishing a workspace to FME Flow: "...The following readers or writers are included in an enabled service, but are not present in the workspace: [ ]...status code 422" FMEFLOW-24867 |
On the Register Services step of publishing to FME Flow, click edit next to each registered service. Remove any readers or writers that are showing as registered, but no longer exist in the workspace. They will be red. |
2026.x 2025.x |
Unplanned |
| Web Connections | FME Form | When FME Flow is used as the connection storage location in FME Form, users without permission to manage connections can see all web services in Form. FMEFORM-33620 |
While visible, the web services remain uneditable without the necessary access. Secrets are masked. If visibility is a concern, please use a personal (default) or shared connection database. |
2025.1 2025.0 |
Resolved 2025.2 |
| Database Connections | FME Form | When FME Flow is used as the connection storage location in FME Form, users without permission to access connections can see database connection details when they have only run access. FMEFORM-33621 |
Note that, while visible, the database connection details remain uneditable without the necessary access. Passwords are masked. If visibility is a concern, please use a personal (default) or shared connection database. |
2025.1 2025.0 |
Resolved 2025.2 |
| Engine Management | FME Flow | After upgrading an FME Flow express installation to 2024.0 or later and restoring a backup containing engine assignment rules, jobs go to the queue and won't run. FMEFLOW-25323 |
Please see Known Issue: Engine Name Change to Localhost Causes Jobs to Queue |
2026.x 2025.x 2024.x |
Unresolved |
| Transformer Attributes | FME Form | Transformers have attributes missing that are unexposed attributes that were previously exposed. Workspaces should continue to run as expected. However, during authoring, attributes appear to be missing, but they are unexposed. FMEFORM-33479 |
While authoring a workspace with an affected transformer, AttributeExposer can restore the expected schema For existing workspaces, run via command line or with FME Workbench despite the warnings. |
2025.x |
Resolved 2025.0.2 |
| Version Control / Upload Workspace | FME Flow | Upon uploading a workspace to FME Flow and committing a version to version control, the user sees the following error: Publish Failed (Not Authorized) - Ensure that credentials are correct, and that user has sufficient privileges. | Grant the user Manage Permissions to Version Control. | 2024.x |
Resolved 2025.0 |
| OpenAIChatGPTConnector Transformer | FME Form | Cannot Open OpenAIChatGPTConnector Version 7 in 2024.2 | Upgrade to 2025.0 or see Known Issue | 2024.2.x |
Resolved 2025.0 |
| Web Connections | FME Form | When FME Flow is used as the connection storage location in FME Form, OAuth 2.0 web connections created from web service templates cannot be used in their respective readers, writers, and transformers. FME Form may also crash when attempting to edit OAuth 2.0 web services. FMEFORM-33427 |
If you need to use OAuth 2.0 web connections, please use a personal (default) or shared connection database. |
2025.0.1 2025.0 |
Resolved 2025.0.2 |
| AttributeManager | FME Form | When attempting to change a large number of attributes all at once from the AttributeManager will cause FME to crash | Upgrade to 2025.0 or see Known Issue: AttributeManager Crashes with Large Bulk Attribute Changes |
2024.x 2023.x |
Resolved 2025.0 |
| GoogleVisionConnector Transformer | FME Form FME Flow |
Transformer fails due to "ImportError: no module found named distutils" at the start of the translation FMEENGINE-84233 |
Upgrade Google AI Services FME package to version 1.6 or newer | 2024.x |
Resolved Upgrade Package |
| GoogleCloudPubSubConnector Transformer | FME Form FME Flow |
Transformer fails due to "ImportError: no module found named distutils" at the start of the translation FMEENGINE-84233 |
Upgrade Google Cloud PubSub FME package to version 2.5 or newer | 2024.x |
Resolved Upgrade Package |
| Encryption | FME Flow | A job with a database connection fails to run on FME Flow. "Encryption Error: AES Decrypt finalization failed" FMEFLOW-21215 |
This is the same root cause as FMEFLOW-23068. Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” | 2023.x |
Resolved 2024.0 |
| Encryption | FME Flow | Changing system encryption settings results in "Error: COM.safe.fmeserver.api.FMEServerException java.lang.illegalArgumentException: Illegal base64 character 3c" FMEFLOW-21215 |
This is the same root cause as FMEFLOW-23068. Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” | 2023.x |
Resolved 2024.0 |
| Automations | FME Flow | When a dynamic workspace with automatic retries is configured within a split-merge block, multiple actions are taken and are not correctly merged when exiting. I.e. for each retry, a failed message will be logged even if a successful run is reached. FMEFLOW-17795 |
None currently. Regular workspace actions act as expected, as well as dynamic workspaces outside of Split-merge blocks |
2026.1 2025.x 2024.x 2023.x 2022.x 2021.x |
Unresolved |
| Jobs | FME Flow | Job fails with the error "Source dataset does not exist" if an input file is uploaded as a temporary upload when running a workspace on the Run Workspace page and the same filename, but a different case, is used (for example, file.txt and FILE.txt) FMEFLOW-23965 |
Rename the input file before uploading it |
2024.x 2023.x 2022.x |
Resolved 2025.0 |
| Publishing to FME Flow | FME Form FME Flow |
When publishing a workspace to FME Server with a web connection that uses Windows Authentication, only the 'Samples' repository is available for selection, even though the user's permissions grant them access to additional repositories on FME Server. FMEFORM-32432 |
Disable the guest account on FME Server |
2024.x 2023.x 2022.x |
Resolved 2025.0 |
| File Upload | FME Flow | Files can be uploaded to FME Flow restricted admin folders by any authenticated account. FMEFLOW-18290 |
See Known Issue: Arbitrary file upload with any authenticated FME Flow account |
2026.x 2025.x 2024.x 2023.x 2022.x |
Workaround |
| Repositories | FME Flow | Internal Server Error when publishing or deleting a repository with a leading or trailing space. FMEFLOW-17417 |
Delete the repository with trailing space from the server share (i.e. from File Explorer). Then delete from Web UI. |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Web Connections | FME Flow | FME Flow web connection in FME Form fails with a 401 error when password begins and ends with a special character (!, &, @, etc.) after initial token expires (approx. 10 days) FMEFLOW-23006 |
Change user password to not include special characters both at the beginning and at the end of the password, such as a special character only at the end, and recreate the web connection |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Temporary Uploads | FME Flow | FME Flow workspace translation fails to find uploaded temp datasets when Engines are distributed across different operating systems FMEFLOW-21985 |
Copy file(s) to the system location where FME is expecting to find it, or first upload the file via the REST API and then call Webhook URL |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Database Connections JDBC |
FME Flow | Manually created JDBC enabled database connections not working with message "No MSSQL_JDBC_NONSPATIAL_2 dataset name was specified (couldn't find a value for MSSQL_JDBC_NONSPATIAL_2_1_DATASET' or MSSQL_JDBC_NONSPATIAL_2_DATASET')", via REST V4 API connection details show empty fields as " " rather than "<Unused>" FMEFLOW-22765 |
Publish connections to FME Flow with the workspace from FME Form, or use the REST V4 API PUT endpoint to change the empty field values from " " to "<Unused>" |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Webhooks | FME Flow | Cannot create a workspace webhook. The OK button is inactive and fields are missing from the Create Webhook page. FMEFLOW-23291 |
This affects workspaces with no published parameters and an SQLCreator or SQLExecutor. Add a published parameter to your workspace, use a native reader/writer, or use an Automation webhook and trigger it via a POST call. |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Schedules | FME Flow | After upgrading FME Flow, my Schedule categories are missing. FMEFLOW-24135 |
Tags are now used instead of categories in FME 2023 and later. Categories will not be migrated to tags, they will need to be recreated after upgrading. See Known Issue: FME Flow Schedule Categories are Not Converted to Tags Upon Migration |
2026.x 2025.x 2024.x 2023.x |
Unplanned |
| ArcGIS Server Feature Service ARCGISPORTALFEATURES. ARCGISONLINEFEATURE, ARCGISFEATURES |
FME Form |
ArcGIS Server Feature Service Writer: Unable to create Feature Services Authentication is not as complete/robust as the AGOL/Portal formats. Users may encounter issues when attempting to authenticate Branch Versioning is not supported FMEENGINE-75760 |
None. |
2026.x 2025.x 2024.x 2023.x |
Unplanned |
| FME Workbench | FME Form | FME 2023.x launches with a toolbar and blank screen (typically on a virtual machine). FMEFORM-29077 |
Downgrade to FME 2022.2 or upgrade VMware Tools to a minimum OpenGL version of 3.3. See Known Issue: FME Workbench 2023 Opens as a Blank Window on a Virtual Machine |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| System Proxy | FME Flow | After supplying updated credentials for a previously configured system proxy, version control will not detect the updated credentials and continues to make requests using the old credentials. FMEFLOW-18251 |
After updating the credentials under System Configuration >Network & Email > Proxy restart the FME Server Core Service. |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| REST API V3 | FME Flow | When transitioning from the V3 API to the V4 API, there is a known issue related to the handling of categories in Schedules. In the V4 API (which the FME Flow 23 UI uses), the concept of categories in schedules has been removed, and tags have been introduced as an alternative. The issue arises when creating a schedule using the V4 API. In the V4 API, a default category is implicitly created and represented by a unique identifier. If this schedule is retrieved using the V3 API, the category listed will be this unique identifier. This may cause issues for users who have built a custom interface using the V3 API. FMEFLOW-16486 |
None |
2026.x 2025.x 2024.x 2023.x |
Unplanned |
| FME Flow Web UI | FME Flow | FME Flow is loading slowly during login in an offline or highly restricted environment. FME Flow is loading the Google Fonts API, which will take around 20 seconds to time out if it cannot be reached. FMEFLOW-21169 |
If possible whitelist fonts.googleapis.com |
2024.0.1 2024.0 2023.x |
Resolved 2024.0.2 |
| Deployment Parameters | FME Flow | Users lacking access permissions for a deployment parameter in FME Flow may encounter the following error: "Undefined macro ‘s3-skytrain-bucket-connection’ dereferenced in file <path to workspace>." | The missing macro is a deployment parameter. Grant the user permission to the deployment parameter. See Getting Started with Deployment Parameters. |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| Automations | FME Flow | A split merge block object is unable to be deleted from an automation canvas. FMEFLOW-23097 |
Save the automation and refresh the page. Now you can select the Split merge block object and delete it |
2024.x 2023.x |
Resolved 2025.0 |
| REST API V3 | FME Flow | Using the REST API V3 GET/schedules only returns the first 100 schedules in the list FMEFLOW-24185 |
Use the REST API V4 GET/schedules endpoint to retrieve schedules |
2025.x 2024.x 2023.2 |
Workaround |
| Tokens | FME Flow | API Token item permissions do not persist on import. For example, access to a specific resource folder. FMEFLOW-24660 |
After restoring an API Token, from a backup or project, reapply the item-level permissions. |
2026.x 2025.x 2024.x 2023.2 |
Unplanned |
| Backup and Restore | FME Flow | Error on system restore after uploading backup (fsconfig) file: "The system restore failed for the following reason: The export location provided is invalid." FMEFLOW-24612 |
This error message may be misleading and could be caused by a gateway timeout when uploading a large backup through a proxy or load balancer in front of FME Flow. Check your browser's developer tools to confirm. Connect to the FME Flow server using the hostname instead, or increase the gateway timeout on your proxy or load balancer to avoid the error. Note: This issue is to resolve the misleading error message. |
2024.x 2023.2 |
Resolved 2025.0 |
| Web Connections | FME Flow | A basic auth FME Flow connection created using the FME Flow web UI, or via the REST v4 API, fails when used in a job with an invalid credentials error. FMEFLOW-24836 |
Publish the connection to FME Flow from FME Form |
2024.x 2023.2 |
Resolved 2025.0 |
| Dropbox Web Service |
FME Form FME Flow |
Newly authorized Named Connections for the Dropbox Web Service will always expire after four hours. FMEENGINE-82114 |
None currently. Web connections and triggers will expire after 4 hours. There is only a workaround for FME Form, by adding the following line to the Web Service's OAuth 2.0 Authorization URL. token_access_type=offline |
2024.x |
Resolved FME Form 2024.1 Resolved FME Flow 2025.0 |
| FME Flow Apps | FME Flow | In a Workspace App, uploading files twice through the 'Browse Resources' menu causes the 'Run' button to disable. FMEFLOW-23580 |
Upload your files directly into the Workspace App using the Drap & Drop method or clicking 'browse file system'. |
2025.0 2024.x |
Resolved 2025.1 |
| Logs | FME Flow | The "Download Logs" option in an Automation's menu does not work on some system locales due to differing date formats. List of known system locales to not work: en_CA, fr_CA, fr_FR, fr, de_DE, de This can also occur if log timestamps have been disabled on your instance. FMEFLOW-24588 FMEFLOW-24607 |
Option 1: Change the system locale on the machine hosting FME Flow to 'en_US' Option 2: Follow along the guide How to Combine Logs for One Automation (FME Flow 2023.2 to 2024.2) |
2026.x 2025.x 2024.x |
Workaround |
| FME Flow | Error validating system email: "Parameter Validation Failed" FMEFLOW-24825 |
There is an error with the email configuration that is not displayed on the web UI. You can use your browser's developer tools to view the error. In FME Flow 2024, the Email From field must only contain an email address. |
2026.1 2025.x 2024.x |
Unplanned | |
| Engine Management | FME Flow | Engine Management: a Job Routing Rule where the source name is a Workspace App name or Automation name doesn't work. FMEFLOW-24872 |
Route based on the repository name that contains the workspace used by the Workspace App. For an Automation, place workspaces in the same repository and route based on the repository name. |
2025.0 2024.x |
Resolved 2025.0.1 |
| Generic Reader | FME Form |
When reading Excel files using a generic reader, the column names are not created as attribute names and data cannot be written downstream. Error: "templateFType" is null FMEENGINE-48449 |
Use a Microsoft Excel reader instead |
2026.x 2025.x 2024.x |
Workaround |
| Python | FME Form | Cannot use Python 3.10+ Conda environments as custom Python interpreter. FME will fall back to using the shipped Python 3.12 interpreter with the error: "The User-specified library <condaEnv>\python312.dll could not be loaded" FMEENGINE-84685 |
Use a Python 3.8 or 3.9 Conda environment. Ensure the Python version is supported by the version of FME used. |
2025.0 2024.x |
Resolved 2025.1 |
| HDFSConnector | FME Form | HDFSConnector fails with the error: "<ModuleNotFoundError>: No module named 'imp'" FMEENGINE-83116 |
Use a custom Python 3.8-3.11 interpreter in Workbench. Note: Python interpreters 3.10+ from Conda environments cannot be used due to FMEENGINE-84685 |
2024.2.2 2024.2.1 2024.2.0 2024.1 2024.0 |
Resolved 2024.2.3 |
| Backup and Restore | FME Flow | After upgrading, no system cleanup tasks are displayed and there is an Internal Server Error message. FMEFLOW-24335 |
This is caused by system cleanup tasks created in earlier versions of FME Flow that are incompatible with FME Flow 2024.2 and later. For example, a cleanup task targeting a UNC path or network resource. In 2025 and later, the internal server error is fixed and legacy cleanup tasks targeting unsupported network paths or resources will be displayed for deletion only (prefixed with $()). You cannot create network cleanup tasks. | 2024.2 |
Resolved 2025.0 |
| Emailer Transformer | FME Form | Error: "SMTPDataError: Could not complete request. Message: (554, b'Transaction failed: Empty address')" when sending email via the Emailer transformer using AWS as the SMTP host. FMEENGINE-84884 |
This affects workspaces authored in earlier versions of FME using Emailer v0 Upgrade the Emailer transformer to v1 Remove and replace the emailer transformer |
2024.2.1 2024.2.0 2024.1 2024.0 2023.x |
Resolved 2024.2.2 |
| Emailer Transformer | FME Form | "401 Unauthorized" when trying to use the Emailer with the template "Microsoft Mail (safe.emailer)" web service and sample Client ID provided. FMEENGINE-84539 |
The sample Client ID is no longer valid. It is always recommended to use your own Client ID. See How to use Microsoft Modern Authentication with FME |
2024.2.1 2024.2.0 2024.1 2024.0 |
Resolved 2024.2.2 |
| Web Connections | FME Flow | Web Connections which use an HTTP Authentication Web Service cannot be uploaded when publishing from Form or edited in the Flow UI. FMEFLOW-24416 |
Use a different web service if possible, store credentials as Deployment Parameters, or edit/create these these connections using the V4 API /connections endpoint. |
2024.2.1 2024.2 |
Resolved 2024.2.2 |
| Resources | FME Flow | FME Flow Linux and FME Flow Hosted Only: 502 gateway error trying to download Resource files greater than approximately 2GB. FMEFLOW-24429 |
For large backups, choose to download the fsconfig instead of saving it to Resources/Backups where it currently can’t be downloaded. For other files, SSH to the FME Flow Linux server and copy files from the system share using the Linux terminal (not applicable for FME Flow Hosted) |
2024.2.1 2024.2 |
Resolved 2024.2.2 |
| Windows Active Directory | FME Flow | When entering a search base, each component is separated by a comma (,) and the seach will fail as the CN value and entries should be parsed as one FMEFLOW-24415 | Upgrade to 2024.2.1 | 2024.2 | Resolved 2024.2.1 |
| Autodesk AutoCAD Reader/Writer ACAD |
FME Form FME Flow |
Jobs with AutoDesk AutoCAD readers/writers using the REALDWG plugin directory fail with the error "Module 'realdwg/REALDWG' is unavailable for use with this FME edition." FOUNDATION-568 FMEENGINE-85174 |
Before attempting this workaround, make a copy of the Flow RealDWG plugin folder (<FMEFlowDir>\Server\fme\plugins\realdwg) so you can undo your changes if necessary. Then, replace the RealDWG plugin folder in FME Flow with the FME Form RealDWG plugin folder (<FMEFormDir>\plugins\realdwg). For workspaces handling DWG files containing only 2D data or where primitive 3D data capabilities are acceptable, use the Autodesk AutoCAD DWG/DXF (ACAD) reader/writer as it does not require RealDWG. FME 2024.2.1 and above uses RealDWG 2025 which is compatible with Windows Server 2019 and above. Upgrade your Windows Server or downgrade FME to 2024.1.4 or below. |
2024.2.0 |
Resolved 2024.2.1 |
| ArcGIS SDE Geodatabase GEODATABASE_SDE |
FME Flow |
ArcGIS SDE Geodatabase error: "Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147216118'. The error message from ArcObjects is: {Bad login user[ ]}", but the same .sde file works outside of FME Flow. FMEFLOW-24789 |
Open the ArcGIS SDE Geodatabase connection in the FME Flow web UI and click OK to resave it. To avoid this error, create the connection via the FME Flow Web UI or upload it when publishing a workspace from FME Workbench. Do not upload from FME Form's Database Connections.
If this doesn't resolve the issue, use the Override Credentials option in the FME Flow UI, save the connection, and run the workspace. Then, disable the Override Credentials option and resave the connection - the connection should work as expected afterwards. |
2024.2.2 2024.2.1 2024.2 2024.1 2024.0 |
Resolved 2025.0 2024.2.3 |
| SQLCreator/SQLExecutor Transformers | FME Form | When reading an Esri Geodatabase using an SQLExecutor or SQLCreator, and ArcGIS Server 11+ is installed on the same machine, no features are read. The warning "Esri Geodatabase: ArcMap has limited SQL functionality and may not be able to process query" is logged, even if ArcMap is not installed FMEENGINE-84276 |
Use an Esri Geodatabase (SDE) reader or FeatureReader transformer |
2024.2 2024.1 2024.0 |
Resolved 2025.0 |
| FME Flow Apps | FME Flow | When an FME Flow workspace app requires authentication, and the app has Database Connection or Web Connection parameters, the authenticated app user is not able to view and select connections they have created. FMEFLOW-23997 |
Use a single, shared connection. If different connections must be available for selection, then an FME Flow administrator needs to grant the app's API token access to each connection. |
2026.1 2025.x 2024.2 2024.1 |
Workaround |
| FME Flow Database | FME Flow | When using the encryptConfigSetting.ps1 power shell script to encrypt the FME Flow database password a NoClassDefFoundError exception is called. FOUNDATION-581 |
The database credentials were recently relocated to a new file, fmeDatabaseConfig.txt, but the script still references the old file, fmeCommonConfig.txt. As a workaround, the file path can be passed as a third parameter like so: .\encryptConfigSetting.ps1 DB_PASSWORD fmeflow 'C:\Program Files\FMEFlow\Server\fmeCommonConfig.txt' |
2024.2 2024.1 |
Resolved 2025.0 |
| Oracle Database Connection ORACLE_DATABASE, ORACLE_SPATIAL,ORACLE_NONSPATIAL |
FME Form | Warning at the bottom of job log: "Resetting a database that is still referenced. (serverType=`ORACLE8i', serverName=` <ServerName>', userName=`<UserName>', password=`***', dbname=`%4'" FMEENGINE-85247 |
This warning is written to the log when a workspace that connects to an Oracle database runs. It has no impact on the job and can be ignored. |
2025.0 2024.2 2024.1 |
Resolved 2025.1 |
| Microsoft OAuth 2.0 | FME Form |
"401 Unauthorized" error when testing a Microsoft OAuth2.0 web service and the optional Client Secret contains a value (Microsoft OAuth2.0 web services) FMEFORM-32432 |
Even if the Client Secret has been set to 'Optional', you must also clear the contents of the field. |
2024.2 2024.1 |
Resolved 2025.0 |
| Backup and Restore | FME Flow | Unable to upload the encryption key file (.jceks) from a Linux client machine, regardless of the Linux distribution or web browser used. Error: "Invalid File Type" FMEFLOW-24291 |
Upload the key file from a Windows or MacOS client machine. |
2026.x 2025.x 2024.2 |
Workaround |
| Web Connections | FME Flow | Web connections not appearing in published parameters FMEFLOW-24586 |
This may occur if you are using a derived web service, which is a web service that is created from a different web service. To fix this, in FME form, find the published parameter, go to supported services, and uncheck all services. Then, reupload the workspace to FME Flow. |
2024.2.2 2024.2.1 2024.2 |
Resolved 2025.0 2024.2.3 |
| Resources | FME Flow |
FeatureWriter cannot write to a Resource connection on FME Flow using an FME Flow parameter (macro). For example: $(mySharedFolder). FMEENGINE-85071 |
One of the following:
|
2026.1 2025.x 2024.2 |
Workaround |
| AttributeExploder Transformer | FME Form | AttributeExploder: drops the last 2 characters of list name FMEENGINE-83608 |
Upgrade to FME 2024.1.2.1 |
2024.1.2.0 2024.1.1 2024.1 |
Resolved 2024.1.2.1 |
| SlackConnector Transformer | FME Form | SlackConnector: upload endpoint has been deprecated by Slack and new Slack apps will not be able to use the upload file functionality. FMEENGINE-82694 |
Upgrade to FME 2024.1.1 |
2024.1.0 2023.x 2022.x 2021.x |
Resolved 2024.1.1 |
| Automations | FME Flow | When submitting an HTTP request with the HTTP Request Automation action, the URL is not encoded correctly or, if already provided as URL-encoded, may be modified by FME Flow and cause the request to fail. FMEFLOW-23729 FMEFLOW-23739 |
Try to provide the Target URL without URL encoding. If the request still fails, use a workspace with an HTTPCaller instead |
2024.1 2024.0 2023.x |
Resolved 2024.2 |
| Automations | FME Flow | A job run by an Automation is stuck in a running status and cannot be canceled via the FME Flow Web UI or REST API. FMEFLOW-22721 |
See Known Issue: Job Submitted from Automation is Stuck Running and Cannot be Cancelled |
2024.1 2024.0 2023.x |
Resolved 2024.2 |
| Automations | FME Flow | When trying to view logs for an Automation, authors receive the error 'You do not have permission'. FMEFLOW-22658 |
Authors cannot view logs by default. Grant access to the Logs folder under Resources. |
2024.1 2024.0 2023.2 |
Resolved 2024.2 |
| Deployment Parameters | FME Flow | A workspace using a deployment parameter that is run via Automation fails with unexpected <opencurly></closecurly> XML tags around the parameter value FMEFLOW-23256 |
Confirm that any deployment parameters used in the Automation have also been shared. If an administrator adds a new deployment parameter after the Automation has been shared, and then updates the Automation to use it, the new deployment parameter must also be shared with anyone who needs to start the Automation. |
2024.1 2024.0 |
Resolved 2024.2 |
| Backup and Restore | FME Flow | After upgrading, the error "Item <workspace name>.fmw does not exist" is displayed on the Subscriptions page. No subscriptions are displayed. This occurs if a workspace used by an FME Workspace Subscription is removed. | Upgrade to FME Flow 2024.2+ or temporarily republish a workspace with the same name to the repository configured in the Subscription and reload the Subscriptions page. The FME Workspace Subscription item can then be updated or removed. |
2024.1 2024.0 |
Resolved 2024.2 |
| Backup and Restore | FME Flow | After upgrading, no publications or subscriptions are displayed, and there is an Internal Server Error message. FMEFLOW-23758 |
Upgrading to FME Flow 2024.2+ resolves some of the issues that cause this problem. If not, please submit a ticket to support for assistance. Also see: FMEFLOW-25422 |
2024.1 2024.0 |
Resolved 2024.2 |
| Microsoft Excel Writer XLSXW |
FME Form | Excel Writer: Field Names row not written FMEENGINE-82549 |
Set the Row Height to 0 on the Feature Type |
2024.1 2024.0 |
Resolved 2024.2 |
| EsriReprojector Transformer | FME Form | EsriReprojector is significantly slower than earlier versions of FME FMEENGINE-83720 |
If you can, use the Reprojector transformer instead. Otherwise, upgrade to FME 2024.2+ |
2024.1 2024.0 |
Resolved 2024.2 |
| FMEFlowJobSubmitter Transformer | FME Form |
Download from Flow window and FMEFlowJobSubmitter only shows first page of Repository folders and the first page of workspaces in 2024.1 FMEFORM-31816 |
Upgrade to FME 2024.1.2 | 2024.1 |
Resolved 2024.1.2 |
| FME Flow Apps | FME Flow | Existing text in text fields for Flow Apps on the Editing Page disappears, but text is still visible from App itself FMEFLOW-22917 |
Use the web browser zoom settings to zoom out one step and text should reappear on App Editing page |
2024.0.1 2024.0 |
Resolved 2024.0.2 |
| PATH Environment Variable | FME Form | Starting In FME 2022.0, Windows installers does not add FME_HOME (FME install directory) to PATH environment variable on Windows. This change could affect users who access FME functionality through Python scripts as required .dll files cannot be located and loaded. DEVOPS-2856 |
Manually add FME install directory to PATH environment variable |
2024.0 2023.x 2022.x |
Resolved 2024.1 |
| Automations | FME Flow | An error is returned when attempting to stop an Automation: "Error: Could not find prepared statement with handle 1." FMEFLOW-22307 |
Restarting FME Flow temporarily resolves the issue. Replace the JDBC driver in the Utilities (<FME Flow Dir>/Utilities/jdbc) folder with version 11.2.1 (mssql-jdbc-11.2.1.jre17.jar) as a permanent solution. |
2024.0 2023.x |
Resolved 2024.1 |
| User Parameters | FME Flow | Conditional/Dependent Visibility user parameters that use operators >, <, <=, >= will be displayed regardless of the options picked. FMEFLOW-20647 |
Change the Conditional/Dependent parameters operators to Is or Is Not |
2024.0 2023.2 2023.1 |
Resolved 2024.1 |
| Encryption | FME Flow | Nothing happens when trying to import an encryption file. There is a 403 error in the web browser's developer tools. FMEFLOW-22786 |
Log in to the FME Flow server. Access FME Flow using localhost in the web browser and try the file upload. |
2024.0 2023.2 |
Resolved 2024.1 |
| Version Control | FME Flow | If a user enabled version control with a Remote Repository URL and then changes to use the local Git repository that comes with FME Flow, they cannot remove the URL from the Web UI. FMEFLOW-21835 |
Use the version control API “http://<hostname>/fmerest/v3/versioncontrol” to update outside of FME Flow (ex: Postman) and provide an empty remote repository URL. |
2024.0 2023.2 |
Resolved 2024.0.1 |
| Packages | FME Flow | A “Python Exception <ImportError>: cannot import name ‘WSCException’ from ‘modules’” error is returned when running workspaces that use older versions of the following packages: Google Cloud Storage (fpkg-google-cloud-storage) Google Cloud PubSub (fpkg-google-cloud-pubsub) Azure Storage (fpkg-azurestorage) EXPERTS-6678 FMEENGINE-80488 |
Upgrade the package in FME Workbench and re-publish the workspace and upgraded package to FME Flow. Run the workspace on the Run Workspace page. | 2024.0 |
Resolved Upgrade Package |
| Remote Engines | FME Flow | When submitting a job to a remote engine that contains a database connection with Conditional or Optional fields or with a SSL Options field, the job submission fails. For error message example see Known Issue: Job Containing Database Connections with Conditional or Optional Fields Fails on Remote Engines. FMEFLOW-22664 |
Have the database connection SSL Mode set to Disable and/or update the connection through the Flow UI. See Known Issue: Job Containing Database Connections with Conditional or Optional Fields Fails on Remote Engines. | 2024.0 |
Resolved 2024.0.1 |
| Automations | FME Flow | Feature counts are not displayed on the Automation canvas for Automation Writers. FMEFLOW-22606 |
None | 2024.0 |
Resolved 2024.1 |
| Web Connections | FME Flow | When trying to authorize an Airtable Web Connection on FME Flow, an error message pops up after entering the Airtable login details: “FME Flow OAuth Service FAILED Failed to complete” FMEFLOW-22682 |
Do not authorize Airtable connection via FME Flow Web UI. Authorize the connection in FME Form and publish to FME Flow. | 2024.0 |
Resolved 2024.0.1 |
| Security | FME Flow | Previously set password fields do not clear to a blank string by selecting the field and then saving it FMEFLOW-21285 |
After selecting the password field, type something into it, then erase it before saving to reset the field to a blank string | 2024.0 |
Resolved 2024.1 |
| Databricks Writer SAFE.DATABRICKS.DATABRICKS_REST |
FME Flow | Unable to locate SAFE.DATABRICKS.DATABRICKS_REST.fmf file for Databricks writer workspace when workspace is published and ran for the first time on FME Flow FMEFORM-30079 FMEFORM-39422 |
Restart FME Flow Engines, republish workspace a second time, manually upload the SAFE.DATABRICKS.DATABRICKS_REST.fmf file to <FMEFlowDir>\Server\fme\metafile\ | 2024.0 |
Resolved 2024.1 |
| WebsocketSender/WebsocketReciever Transformers | FME Flow | WebsocketSender and WebsocketReciever transformers have been depreciated and will display the following error if used: WebSocketSender: The WebSocketReceiver/Sender transformers are no longer supported FMEENGINE-81231 |
Update workflows to use FME Flow Automation WebSockets or the PythonCaller. | 2024.0 |
Deprecated 2024.0 |
| FME Flow Connections |
FME Form FME Flow |
When an FME Form version from 2024.0 to 2024.2.0 is installed on Windows Server 2016 or Windows Datacenter 2016, and an attempt is made to connect to FME Flow hosted on a different machine with a newer Windows Server version and configured with HTTPS, the connection fails with an error FMEFORM-31805 |
See Known Issue: FME Form HTTPS Connection Fails on Windows Server 2016 |
2024.2.0 2024.1 2024.0 |
Resolved 2024.2.1 |
| Slack Web Connection | FME Form | "this browser won't be supported" message appears when creating a Slack web connection FMEENGINE-81729 |
Create a new web connection in FME Workbench from the Slack template. Under Authorization Parameters > HTTP User Agent > and change the default value to 'FME Default' |
2023.x 2022.x 2021.x 2020.x |
Resolved 2024.0 |
| Webhooks | FME Flow | When a workspace webhook is created with a geometry parameter and then run, the translation fails due to a JSON syntax error. FMESERVER-19915 |
On the create webhook page, re-select the geometry parameter to update the webhook URL prior to saving. |
2023.x 2022.x |
Resolved 2024.0 |
| User Parameters | FME Flow | When running a workspace on FME Server with a geometry parameter or using the workspace in an FME Server app, the extent of the area shown is larger than the bounds defined in FME Workbench when the geometry parameter is viewed ‘inline’ | Use the pop-up map window instead of the inline map. |
2023.x 2022.2 2022.1.3 2022.1.2 |
Resolved 2024.0 |
| Esri ArcGIS Layer Reader ARCGIS_LAYER |
FME Form | The Esri ArcGIS Layer Reader fails to bring up an input dataset selection dialog when selecting the ellipsis button with the error message that "Selecting Esri layers is unavailable". FMEENGINE-80772 FMEENGINE-67049 |
Instead of selecting from the ellipsis button, provide a known dataset path to the layer file. |
2023.x 2022.2 |
Resolved 2024.0 |
| Esri Shapefile Writer SHAPEFILE |
FME Form | When writing an Esri shapefile in FME Desktop 2022.1 through FME Form 2023.0, users whose machines are set to a Japanese system locale (OS Locale: ja_JP, for example) will notice the attribute names in the output shapefiles are prefixed with ‘Q_’ anytime the source attribute name begins with a Japanese character. FMEENGINE-76609 |
See Known Issue: SHAPEFILE Writer Adds 'Q_' Prefix to Attribute Names Beginning With Japanese Characters |
2023.0 2022.2 2022.1 |
Resolved 2023.1 |
| FME Workbench | FME Form | FME Form does not load successfully. When opening FME Workbench, it starts up with the splash-screen as normal, but after "Initializing main window" the application does not load. FMEFORM-28857 |
Upgrade to FME 2024.0, or see workaround. | 2023.x |
Resolved 2024.0 |
| FME Form Licensing Assistant | FME Form | Users that add new floating license seats to an existing serial number, or request a license file with multiple serial numbers are getting licenses in two or more line items. This creates two or more “FME Form” license pools in the Licensing Assistant when there should only be one. DEVOPS-3164 |
Requesting an FME 2023 license will give you a license file wherein all editions associated with the serial number(s) are consolidated into a single edition called “FME Form”. | 2023.x |
Resolved Other |
| FeatureWriter Transformer | FME Form | FeatureWriter: when there are multiple FeatureWriters in a workspace, performance is much slower than in prior FME versions. FMEENGINE-81646 |
Set the 'Features to Read' to 'Data Features'. If you require the schema as well, obtain it from a separate FeatureReader set to 'Schema Features' and initiate it with a single feature (for example, using a sampler) | 2023.x |
Resolved 2024.0 |
| FeatureJoiner Transformer | FME Form | FeatureJoiner crashes FMEENGINE-81599 |
Adding a Decelerator before the Left port might help. (set "Delay Per Feature (Seconds)" to 0) | 2023.x |
Resolved 2024.0 |
| REST API V4 | FME Flow | In REST API V4, the /permissions endpoint will now reference ids instead of names when setting permissions. This change will mainly affect users who this endpoint to set permissions for Flow Apps or Schedules. FMEFLOW-18384 |
Use ids instead of names in REST calls. Refer to the REST API V4 documentation for more details. |
2026.x 2025.x 2024.x 2023.x |
Workaround |
| FME Workbench | FME Flow | When a workspace with an Overview (created in FME Workbench Navigator window > Description > Overview) is being configured to run with Run Workspace on FME Flow, the Overview does not appear beneath the selected workspace. FMEFLOW-21824 |
Upgrade to FME 2024.0 | 2023.x |
Resolved 2024.0 |
| Jobs | FME Flow | Non-admin users with applicable permissions (Jobs > Manage) cannot filter Jobs by User | Enable Manage permissions for Engines and Licensing for applicable users/roles | 2023.x |
Resolved 2024.0 |
| Automations | FME Flow | When copying/pasting the Run Workspace Action node in Automations, the Repository, and Workspace parameters are unavailable/missing. FMEFLOW-21623 |
Add a new Action node to the canvas instead of copying/pasting. | 2023.x |
Resolved 2024.0 |
| Backup and Restore | FME Flow | System Backup fails with the error "929029: unable to export" FMEFLOW-23068 |
Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” | 2023.x |
Resolved 2024.0 |
| MapTextLabeller Transformer | FME Flow | Error when trying to use the MapTextLabeller on FME Flow: "Module 'LabelEZFactory' is unavailable for use with this FME edition" FMEDIST-829 |
Downgrade to FME Flow 2023.1.x or upgrade to 2023.2.5. Please note that 2023 is the last major FME version to include the MapTextLabeller. Please see MapTextLabeller Plugin Availability Changes |
2023.2.4 2023.2.3 2023.2.2 2023.2.1 2023.2.0 |
Resolved 2023.2.5 |
| Dyanmic Writer | FME Form | Dynamic Writers produce excessive warning messages about the renaming of format attributes when set to Dynamic Mode and there is a performance loss. FMEENGINE-80292 |
Upgrade to 2023.2.2 or turn off Log Warnings in FME Workbench (this will suppress all other warnings as well) |
2023.2.1 2023.2.0 2023.1 2023.0 |
Resolved 2023.2.2 |
| Automations | FME Flow | When passing JSON parameters to an email subscriber using an FME Flow Topic action in an Automation, the email body contains the full JSON instead of the subscriber content specified in the JSON. FMEFLOW-21252 |
This occurs when the topic message is passed as a JSON parameter in the FME Flow Topic action. Hardcode the topic message JSON in the Automation or use the FMEFlowNotifier transfomer in FME Workbench to pass the JSON as an attribute. |
2023.2 2023.1 2023.0.2 2023.0.1 |
Resolved 2024.0 |
| Projects | FME Flow | Project export fails when the destination default value path set in a Workspace app doesn't exist FMEFLOW-22570 |
Run the workspace with the Job Submitter service first to ensure the resource path is created before creating the project. Another option is to have the default path point to an existing data resource folder. |
2023.2 2023.1 |
Resolved 2024.0 |
| Backup and Restore | FME Flow | The FME Flow Backup and Restore does not restore Database and Web Connections on systems that use custom encryption. FMEFLOW-21709 |
Switch to the weak encryption mode before performing the backup and restore. Please contact support if you have questions. |
2023.1.2 2023.1.1 |
Resolved 2023.2 |
| Python | FME Form | If Anaconda3/ Miniconda3 Python 3.11 is installed on the same machine and Anaconda/ Miniconda is registered as the default Python 3.11, any FME package installation will fail with the error: ImportError: DLL load failed while importing _ctypes: The specified module could not be found. Error in running the Python command 'python %0' FMEENGINE-80576 |
Copy <anaconda InstallDir>/ Library/bin/ffi.dll to <anaconda InstallDir>/ DLLs *Requires administrative permissions if Anaconda/Miniconda is installed for all users (ie. installation path is in %programdata%) OR downgrade to Anaconda/ Miniconda Python 3.10 |
2023.1.1 2023.1.0 2023.0 |
Resolved 2023.1.2 |
| Python | FME Form | Users with a custom Python 3.7 to 3.9 interpreter set in FME Form will encounter this warning: FME supports Python 3.7 to 3.11. Ignoring the user-specified Python library version 3.0 from <pathToCustomInterpreter.dll> FMEENGINE-80724 |
Upgrade to 2023.1.2+ |
2023.1.1 2023.1.0 |
Resolved 2023.1.2 |
| Aggregator Transformer | FME Form | Aggregator doesn't respect Group By setting when receiving 10,000 features or more FMEENGINE-80344 |
Use a Decelerator before the Aggregator or use FME 2023.0 | 2023.1.0 |
Resolved 2023.1.1 |
| FME Workbench | FME Form | Transformer Order in the Navigation Panel - Not Alphabetical FMEFORM-29414 |
None. | 2023.1.0 |
Resolved 2023.1.1 |
| FME Workbench | FME Form | List of upgradeable, invalid or disabled transformers does not appear in the Navigator Pane for workspaces in FME 2023.1+ FMEFORM-29429 |
None. | 2023.1.0 |
Resolved 2023.1.1 |
| SAML | FME Flow | When the FME Flow web UI is accessed via FQDN, SAML login attempt [ after typing in the IDP credentials and submitting] takes us back/loops to the IDP login prompt webpage. SAML works well after replacing the flow host FQDN with IP address. FMEFLOW-21670 |
Reference the flow/server host with IP address instead of the FQDN [i.e. FME_SERVER _WEB_URL field in fmeServerConfig.txt and fmeServerWeb ApplicationConfig.txt] Setup the SAML configuration with the IP address instead of the FQDN. |
2023.1 2023.0 2022.2 |
Resolved 2023.2 |
| Deployment Parameters | FME Form | Replacing a deployment parameter in the database connection of a reader/writer with a connection from FME Workbench will leave an invalid deployment parameter entry in Navigator. The reader/writer will then continue to use the old connection associated with the deployment parameter instead of the newly chosen connection. FMEFORM-29101 |
Remove the reader/writer, restart FME Workbench, re-add the reader/writer |
2023.1 2023.0 |
Resolved 2023.2 |
| Oracle Writer ORACLE_DATABASE |
FME Form | Oracle Writer fails to create table with more than 100 attributes. Error: 'Too many values to bind'. FMEENGINE-79926 |
None. |
2023.1 2023.0 |
Resolved 2023.2 |
| AutodeskDocsConnector Transformer | FME Form | The AutodeskDocsConnector and web service stops working in existing workspaces and newly created web connections due to Autodesk's planned OAuth v1 deprecation. FMEENGINE-79894 |
Upgrade FME to 2023.2 and update the AutodeskDocs package to v1.1.0 or newer. See Known Issue: AutodeskDocsConnector OAuth API v1 Deprecation will Require an Upgrade to FME 2023.2 |
2023.1 2023.0 |
Resolved 2023.2 |
| FeatureWriter Transformer | FME Form | FeatureWriter: Workbench unresponsive after importing feature type FMEFORM-29677 |
None. |
2023.1 2023.0 |
Resolved 2023.2 |
| Active Directory | FME Form | Installing FME Form 2023.0 through 2023.1.x breaks Windows AD auth in other installed 32-bit applications, with one of the following generic error messages shown: Failure to access the DBMS Server unable to load adalsql.dll FMEENGINE-80806 |
Upgrade FME Form to at least FME Form 2023.2, or download and install the Microsoft OLE DB Driver for SQL Server v. 19.3.1+. The issue lay in a bug that was discovered with the OLE DB Driver v19.2. |
2023.1 2023.0 |
Resolved 2023.2 |
| FME Flow Apps | FME Flow | A file parameter placed in a parameter group doesn't allow uploads in an FME Flow app. FMEFLOW-21415 |
In FME Workbench, create a new workspace and create the file parameter(s) outside of the parameter group. |
2023.1 2023.0 |
Resolved 2023.2 |
| FME Flow Apps | FME Flow | Cannot save an FME Flow app that has required parameters in a parameter group unless default values are provided. FMEFLOW-21278 |
In FME Workbench, move the parameters outside of the group. Or, on the FME Flow Create/Edit App page, provide default values. |
2023.1 2023.0 |
Resolved 2023.2 |
| Users and Roles | FME Flow | Authorized users and roles do not save when 'Require Authentication' is enabled for a Flow app (any type). This affects installations with a large number of users and roles. FMEFLOW-21659 |
Access can be granted via user management > items > category > choose the type of app you want to grant access to > grant permissions. If the Flow app is saved after permissions are applied via user management, the permissions will need to be reapplied. |
2023.1 2023.0 |
Resolved 2023.2 |
| SQLExecutor Transformer | FME Flow | Job with SQL Executor completes successfully, but the SQL does not run. | This occurs when there is no transformer connected after the SQLExecutor. Connect a logger to the Result port. |
2023.1 2023.0 |
Resolved 2023.2 |
| Web Connections | FME Form | Remove JCEKS description keys from FME 2023.1 For the customers migrating from FME 2018 to FME 2023.1, all the database and web connections will not work. FMEFORM-13391 |
First upgrade from FME 2018.x to a build between FME 2019.0 to FME 2023.0, all the existing connections/web services will get migrated without any issue. |
2023.1 2019.x 2018.x |
Resolved 2023.1 |
| Users and Roles | FME Flow | Incorrect users and type listed when searching for roles in User Management FMEFLOW-21878 |
Scroll to the role you want to view details for. If you have a large number of roles, use the GET /security/roles/< role > REST API endpoint | 2023.1 |
Resolved 2023.2 |
| FME Flow Web UI | FME Flow | FME Flow web UI search results are inaccurate in the following places: User Management Roles: Users and Type Automations: Last Updated Flow Apps: Last Updated Automation Apps: Expiration’ Gallery Apps: Number of Links Resources: Date and Size System Cleanup: Max Age, Filter, and Enabled Broadcast Messages: Severity and Last Updated FMEFLOW-21879 |
Increase the number of visible items on the page and use your web browser's search feature instead. If there are too many items to display on one page and the web browser search cannot be used, then you may be able to access some item lists using the REST API and export the results to a file for searching. | 2023.1 |
Resolved 2023.2 |
| Security | FME Flow | Password reset email doesn't get sent to users when using "Forgot your password?" on the web UI login page FMEFLOW-21880 |
Login to FME Flow with an admin account and manually change the users password from the User Management page. | 2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | Automation Workspace Action: parameter selections do not persist if manual trigger parameters are provided as values for Date, Datetime, or Yes/No fields FMEFLOW-21896 |
Hardcode the parameter values in the automation action. | 2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | Automation Log Action not logging Manual Trigger parameter values | Use a Logger transformer in a workspace | 2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | When passing an Automation parameter to a password parameter in a workspace action, the parameter's JSON name is passed to the workspace, not the value FMEFLOW-21897 |
Hardcode the password value in the automation action. | 2023.1 |
Resolved 2023.2 |
| Security |
FME Flow FME Flow Hosted |
Weaknesses in the encryption scheme used for encrypting secrets in FME Flow (formerly FME Server) could be exploited to allow an attacker to gain unauthorized access to the server or environment. FMEFLOW-18670 FLOWHOSTED-2149 |
Upgrade to 2023.1+. See Known Issue: FME Flow Secrets Encryption Weakness |
2023.0 2022.x 2021.x 2020.x |
Resolved 2023.1 |
| Azure Active Directory or SAML | FME Flow | In FME Server 2021.2 to 2022.2 and FME Flow 2023.0, it is possible for an unauthenticated attacker to gain access to the application, leading to system compromise without requiring user interaction. This only affects instances with Azure Active Directory (AD) or SAML user accounts imported to FME Flow. FMEFLOW-21273 |
Upgrade to 2023.1+. See Known Issue: FME Flow Authentication Bypass Vulnerability in Instances with Imported Azure AD/SAML Accounts |
2023.0 2022.x 2021.x |
Resolved 2023.1 |
| Projects | FME Flow | Project import overwrites existing web service even when a web connection is excluded from the import FMEFLOW-21858 |
Update to 2023.2 | 2023.1 |
Resolved 2023.2 |
| Python | FME Flow | Python scripts using numpy fail on FME Flow when they worked on FME Form. FMEFLOW-21194 |
Please open a support case and provide which version of FME you are on and the operating system you are using and we can provide a workaround. |
2023.0.2.0 2023.0.1.x |
Resolved 2023.0.2.1 |
| Distributed Engines | FME Flow | When installing a Distributed Engine the engine service will not start because of a missing file. DEVOPS-4057 |
Use FME 2023.0.2 or later, or download and place the fmeserver.config into the following directory: <Install Directory> FMEFlow\ server\ security | 2023.0.1 |
Resolved 2023.0.2 |
| Schedules | FME Flow | Schedule fails to submit jobs after changing or transferring ownership to another user. In Resources>Logs>core>current>fmescheduler.log, you will see warning and error messages: WARN FMEServerQuartzScheduler_Worker-4 406427 : Job submission failed. Category: <category> Name: <ScheduleName> Error: <ScheduleName> WARN FMEServerQuartzScheduler_Worker-4 406411 : Job submission failed. Please ensure Transformation Manager is available. Category: <category> Name: <scheduleName> ERROR pool-2-thread-1 406439: An error occurred while triggering: QSInvalidRequest FMESERVER-18525 |
Open each schedule where the ownership has been changed and resave them. |
2023.0.0.2 2023.0.0.1 2023.0 2022.x 2021.x |
Resolved 2023.0.0.3 |
| Microsoft Excel Writer XLSXW |
FME Form | Excel Writer currently deletes the existing file, when 'overwrite existing' is enabled in the writer parameters. FMEENGINE-78316 |
Disable overwrite existing file. |
2023.0.0 2022.2.6 |
Resolved 2023.0.1 |
| Esri Licensing | FME Form | Esri Licensing not working with ArcServer if ArcServer and Pro are both installed. FMEENGINE-77154 |
Uninstall either ArcPro or ArcServer and restart FME. Please contact Safe Software Support if you require a different workaround. |
2023.0 2022.2.6 2022.2.5 2022.2.4 |
Resolved 2023.1 |
| Log Files | FME Flow | The DateTime format in the FME Server Log Files has changed from Mon-18-Jul-2022 01:48:26.085 PM to Mon.-18-Jul.-2022 01:48:26.085 p.m. FMEFLOW-18681 |
None. This is caused by upgrading FME Server from JDK 8 to JDK 17. This change is only present for certain locales. For example, on a system where the default locale is en_US the DateTime format will not be affected, but if the default locale is en_CA. |
2023.0 |
Unplanned Other |
| Floating License | FME Form | In FME Form 2023.0 licensed with a floating license server. Using existing or new FME workspaces with transformers/custom transformers configured to use parallel processing generates an error FMEENGINE-78741 |
See Known Issue: FME 2023 fails to invoke parallel processing when using a Floating License | 2023.0 |
Resolved 2023.0.1 |
| Automations | FME Flow | When trying to create a webhook trigger, the web UI reports that the webhook URL is required and won’t let you create the trigger. The webhook URL is generated by FME Flow after the automation is saved and shouldn’t require any user input. FMEFLOW-21011 |
Enter any text in the URL field to create the trigger. The automation then replaces the text on save with the generated webhook URL. | 2023.0 |
Resolved 2023.1 |
| ArcGIS Portal Service Web Connection ARCGISPORTALFEATURES |
FME Form | When trying to create a web connection for ArcGIS Portal 11.1, the process fails with the error: Unable to retrieve access token FMEFORM-28714 |
To create an ArcGIS Portal 11.1 web connection, upgrade to at least FME 2022.2.7 b22801 or later. You must also define a new web service - ArcGIS Portal web services defined in prior versions of FME will not work. See Known Issue: FME fails to create a portal web connection to ArcGIS Enterprise 11.1 |
2023.0.0.1 2023.0.0.0 2022.2.6 |
Resolved 2023.0.1 2022.2.7 |
| Web Connections | FME Flow | Error message when trying to connect from Form to Flow through a Flow web connection: "Register client failed (Not Authorized) - Ensure that credentials are correct, and that user has sufficient privileges." FMEFLOW-24425 |
In FME Flow go to User Management > User/Roles. Grant Access permission for Deployment Parameters. |
2026.x 2025.x 2024.2.3 2024.2.2 2024.2.1 |
Unplanned |
| FME Flow Installation | FME Flow | The FME Flow installer hangs and will not complete DEVOPS-4045 DEVOPS-3945 |
See Known Issue: PowerShell Execution Policy Prevents Installation of FME Flow |
2024.0 2023.x 2022.2 |
Resolved 2024.1 |
| Backup and Restore | FME Flow | System restore fails with key constraint error related to users, roles, or tenants, for example: "fme_useraccount_assigned_role_pkey" or "fme_azure_ad_user_tenant_id_id_key" FMEFLOW-24891 |
If you have configured a Windows or Azure AD authentication service before doing a system restore, disable synchronization and reattempt the restore If you are doing an upgrade and still have access to the old FME Flow instance, disable synchronization on the authentication service and then create a new backup. Reattampt the restore. If the restore continues to fail, please submit a ticket and include your fsconfig (backup file), if possible |
2024.2 |
Resolved 2025.0 |
| Remote Engines | FME Flow | When a connected remote engine host is rebooted, the remote engine connection on the core host continues to show “Not ready” or “Offline” even after the remote engine host comes back online. The jobs remain queued on the Flow host. FMEFLOW-23273 |
Deleting the current remote engine connection on the core host and recreating the same connection solves the issue. | 2024.0 |
Resolved 2024.1 |
| Active Directory | FME Flow | When configuring an Active Directory connection and selecting the SASL mechanism = GSS-SPNEGO , the user is not able to access the 'Authentication Services' web page. A message pops up stating “Internal Server error” [HAR log says 500 Internal error] and the screen stays greyed out with the “thinking” wheel. The fmedirectoryserver.log mentions error "Unsupported SASL mechanism 'GSS-SPNEGO'". FMEFLOW-22604 |
Please contact us for further assistance. | 2023.2 |
Resolved 2024.0 |
| Databricks Connection DATABRICKS_JDBC |
FME Flow | When importing a project or restoring a backup that contains a Databricks connection created in FME 2023.1, the connection is not restored. There is no indication of that the Databricks connection has been skipped in the migration log. Note: this bug only affects FME Flow 2023.1 instances that have not previously had a Databricks connection published. FMEFLOW-21339 |
Publish a new Databricks connection to the FME Flow instance prior to importing a package or restoring a backup that contains Databricks connections. Or, manually recreate the Databricks connection. | 2023.1 |
Resolved 2023.2 |
| Apache Tomcat | FME Flow | FME Flow does not utilize the X-Frame Options header meaning an attacker can exploit vulnerabilities such as clickjacking. FMESERVER-10761 FMEFLOW-26086 |
See Known Issue: FME Flow Apache Tomcat Vulnerability with X-Frame-Options header |
2026.x 2025.x 2024.x 2023.x 2022.x 2021.x 2020.x 2019.x 2018.x |
Unplanned
|
| Engines | FME Flow | FME Flow Starts Two Engines by Default FMEFLOW-13819 |
See Known Issue: FME Flow Starts Two Engines by Default |
2024.1 2024.0 2023.x 2022.x 2021.x 2020.x |
Resolved 2024.2 |
| Backup and Restore | FME Flow | When upgrading FME Flow from 2021 to 2023 and performing a backup and restore, User Management > Authentication Services is inaccessible and returns an Internal Server Error. FMEFLOW-21836 |
See Known Issue: Authentication Services Page Gives 500 Internal Error after 2021 to 2023 Backup and Restore |
2023.1 2023.0 2022.x 2021.x |
Resolved 2023.2 |
| Esri Geodatabase Writer GEODATABASE_FILE |
FME Form | While trying to publish a feature class written to file geodatabase in FME Form 2023.1 with an ArcGIS Pro 3.1.x license, users an error message in the Share As Web Layer geoprocessing pane of ArcGIS Pro 3.1.x after selecting Analyze FMEENGINE-80435 |
See Known Issue: File Geodatabases Written in FME Form 2023.1 with ArcGIS Pro 3.1.x Will Not Publish to ArcGIS Portal 11.0 |
2023.2 2023.1 |
Resolved 2024.0 |