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

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

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

Unplanned

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

2024.0

Unresolved