Known Issues in FME 2024.x

FMEENGINE-82535

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

Use an Excel reader instead

2024.0

Unplanned

Excel Writer: Field Names row not written

Set the Row Height to 0 on the Feature Type

2024.0

Unplanned

OBJ Reader: textures rende/appear black

Upgrade 

2024.0 Build 24154

FME Form 2024.0 Build 24151

Newly authorized Named Connections for the Dropbox Web Service will always expire after four hours.

Add the following line to the Web Service's OAuth 2.0 Authorization URL.

2024.0

2024.1

SlackConnector: upload endpoint has been deprecated by Slack and new Slack apps will not be able to use the upload file functionality.

Upgrade when available

2024.1 and older

Planned for 2024.2

"this browser won't be supported" message appears when creating a Slack web connection

Create a new web connection in workbench from the Slack template.

Under Authorization Parameters > HTTP User Agent > and change the default value to 'FME Default'

2023.1

Unplanned

Download from Flow window and FMEFlowJobSubmitter only shows first page of Repository folders and the first page of workspaces in 2024.1

2024.1

2024.1.2

AttributeExploder: drops the last 2 characters of list name

2024.1

2024.1.2.1

"401 Unauthorized" when trying to use the Emailer with the template "Microsoft Mail (safe.emailer)" web service and sample Client ID provided.

The sample Client ID is no longer valid. It is always recommended to use your own Client ID. Please see How to use Microsoft Modern Authentication with FME

2024.0

Unresolved

"401 Unauthorized" error when testing a Microsoft OAuth2.0 web service and the optional Client Secret contains a value (Microsoft OAuth2.0 web services)

Even if the Client Secret has been set to 'Optional', you must also clear the contents of the field.

2024.1

Unresolved

EsriReprojector is significantly slower than earlier versions of FME

If you can, use the Reprojector transformer instead. Otherwise, upgrade to FME 2024.2+

2024.0

2024.2

When reading an Esri Geodatabase using an SQL Executor or SQL Creator, 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

Use an Esri Geodatabase (SDE) Reader or FeatureReader

2024.0

Unresolved

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.

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

Unplanned

See FOUNDATION-568 if your version is below 2024.2.1

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

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

Unplanned

FMEFLOW-17417

Internal Server Error when publishing or deleting a repository with a leading or trailing space.

Delete the repository with trailing space from the server share (i.e. from File Explorer). Then delete from Web UI.

2023.0

Unplanned

FOUNDATION-568

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

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

2024.2.0

2024.2.1

EXPERTS-6678
FMEENGINE-80488

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)

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

Unplanned

FMEFLOW-22664

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. See this article for examples of error messages returned.

Have the database connection SSL Mode set to Disable and/or update the connection through the Flow UI. 

See here for more information.

2024.0

2024.0  Build 24192

FMEFLOW-21796

When trying to view logs for an Automation, authors receive the error 'You do not have permission'.

Authors cannot view logs by default. Grant access to the Logs folder under Resources.

2023.2

Unplanned

FMEFLOW-22786

When trying to import an encryption file, nothing happens. There is a 403 error in the web browser's developer tools.

Log in to the FME Flow server. Access FME Flow using localhost in the web browser and try the file upload. 

2023.2

2024.1

Feature counts are not displayed on the Automation canvas for Automation Writers.

none

2024.0

2024.1

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.

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.

2023.2

2024.0 b24194

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”

Do not authorize Airtable connection via FME Flow Web UI. Authorize the connection in FME Form and publish to FME Flow.

2024.0

2024.0 b24189

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

2024.2

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

Restart FME Flow Engines, republish workspace a second time, manually upload the SAFE.DATABRICKS.DATABRICKS_REST.fmf file to <FMEFlowDir>\Server\fme\metafile\

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

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.

Newly authorized Named Connections for the Dropbox Web Service will always expire after four hours.

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

Jobs do not route to the correct queue if a routing rule based on role is used and the job is submitted via an FME Flow Workspace App with authentication enabled.

This is limited to workspace apps. If feasible, set the rule based on user instead of role. Otherwise, choose a different property to route the job or have authenticated users submit the job via Run Workspace instead.

2022.0

In a Workspace App, uploading files twice through the 'Browse Resources' menu causes the 'Run' button to disable.

Upload your files directly into the Workspace App using the Drap & Drop method or clicking 'browse file system'.

2024.0

FMEFLOW-23729

FMEFLOW-23739

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. 

Try to provide the Target URL without URL encoding. If the request still fails, use a workspace with an HTTPCaller instead

2023.0

FMEFLOW-23273

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.

Deleting the current remote engine connection on the core host and recreating the same connection solves the issue.

2024.0
2024.1

FMEENGINE-81231

WebsocketSender and WebsocketReciever transformers have been depreciated and will display the following error if used: 
WebSocketSender: The WebSocketReceiver/Sender transformers are no longer supported

Update workflows to use FME Flow Automation WebSockets or the PythonCaller.

2024.0

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. 

Please see Known Issue: Job Submitted from Automation is Stuck Running and Cannot be Cancelled

2023.0

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.

None currently. Regular workspace actions act as expected, as well as dynamic workspaces outside of Split-merge blocks

2022.0

Unresolved

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)

Rename the input file before uploading it

2022.0

Unresolved

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.

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.

2024.0

Unresolved

Restoring a backup from 2020 or 2021 will not restore the Tools repository (which may contain user-created workspaces) and presents no errors in the logs

1. Before backup, publish workspaces to a different repository, then after restore, create the Tools repository and re-publish workspaces there

2. If access to the source server is lost, open the fsconfig file by renaming it to a .zip extension, find the workspace in the files folder and re-publish to the new instance (after creating the Tools repository)

2020.0

Unplanned

Using the REST API V3 GET/schedules only returns the first 100 schedules in the list

Use the REST API V4 GET/schedules endpoint to retrieve schedules

2023.2

Unresolved

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

2024.2

After upgrading, no publications or subscriptions are displayed and there is an Internal Server Error message.

Upgrade to FME Flow 2024.2+ or submit a ticket to support for assistance and reference Known Issue ID FMEFLOW-23758.

2024.0

2024.2

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"

Upload the key file from a Windows or MacOS client machine.

2024.2

Unresolved

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. 

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. 

2024.1

Unresolved

Web connections that use an HTTP Authentication Service web service cannot be edited on Flow. Also, the  connection's username and password are missing in FME Flow after it has been uploaded from FME Form.

• Use a token or Oauth2.0 web service, if possible, or
• Embed credentials into the reader/writer/transformer in FME Workbench and then republish to FME Flow

2024.2

Unresolved

FME Flow Linux and FME Flow Hosted Only: 502 gateway error trying to download Resource files greater than approximately 2GB. 

• 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

Unresolved

After upgrading, no system cleanup tasks are displayed and there is an Internal Server Error message.

2024.2

Unresolved

FOUNDATION-581

When using the encryptConfigSetting.ps1 power shell script to encrypt the FME Flow database password a NoClassDefFoundError exception is called.

The database credentials were recently relocated to a new file, fmeDatabaseConfig.txt, but the script is still referencing 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.1

Planned for 2025.0

Web connections not appearing in published parameters

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

Unresolved

API Token item permissions do not persist on import. For example, access to a specific resource folder.

After restoring an API Token, from a backup or project, reapply the item-level permissions.

2023.2

Unresolved

FMEENGINE-85071

FMEFORM-32709

Cannot write to a Resource connection on FME Flow using an FME Flow parameter (macro). For example: $(mySharedFolder). This occurs with the FeatureWriter and may occur with some native writers as well.

• If possible, try to use a native writer, like the csv writer, instead of the FeatureWriter.
• Save the FME Flow resource parameter (macro) to an attribute and reference the attribute in the FeatureWriter's dataset path.

2024.2

Unresolved

FMEFLOW-24699

Error on system restore after uploading backup (fsconfig) file:

"The system restore failed for the following reason: The export location provided is invalid."

2023.2

Unresolved

FMEFLOW-24425

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

2024.2.1, 2025.0

Unresolved

FMEENGINE-85174

See FOUNDATION-568 if your version is below 2024.2.1

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

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

Unplanned

Warning at the bottom of job log:

"Resetting a database that is still referenced. (serverType=`ORACLE8i', serverName=` <ServerName>', userName=`<UserName>', password=`***', dbname=`%4'"

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.

2024.1

Unresolved

FMEFLOW-24588

FMEFLOW-24607

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

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) and change the DateTimeConverter in the provided workspace to follow your system locale's datetime format.

2024.2

Unplanned