Skip to main content
Question

Upgraded FME FLOW to 2026.3: Worspace apps with file uploads only accepts some files

  • Oct 29, 2026 1:32 PM UTC
  • 4 replies
  • 61 views

havmoejbv
Supporter
Forum|alt.badge.img+16

I have a set of workspace apps on our Flow to convert data between file formats. After upgrading our installation in test, I experience some strange behaviour: While uploading data to convert, some files are accekted, while others are rejected. 

 

Looking into the network data using the developer tools, I find that the accepted files gives a response like this:

{"serviceResponse": {
"statusInfo": {"status": "success"},
"session": "3cc570c6-2d66-4d66-86af-22c6a2f56696",
"files": {
"path": "",
"file": [
{
"size": 1531,
"name": "file name.kof"
}
],
"folder": [{"name": ""}]
}
}}

The rejected files gives this response:

<html>
<head>
<title>Request Rejected</title>
</head>
<body>
The requested URL was rejected. Please consult with your administrator.<br>
<br>
Your support ID is: 12358467762813340<br>
<br>
<a href='javascript:history.back();'>[Go Back]</a>
</body>
</html>

Have anyone experienced this? Any tips on what could be causing this? 

I see this on several workspaces with different input file formats

4 replies

nickcumming
Safer
Forum|alt.badge.img+14

Hi @havmoejbv,

I believe I’ve pinned this down. I don't think the “Request Rejected” page is coming from FME Flow - it would return JSON. It’s likely the block page from a web application firewall (it looks like ASM F5) sitting in front of your server. Are you testing the upgrade in a WAF controlled environment?

Try sending the support ID to your network/security team. They can look the support ID up in the WAF logs and verify that’s where the files are snagged. In the logs they can see exactly which rule fired and add an exception for the Flow upload endpoints. I hope this helps with the upgrade. Reach out if you have any questions.


havmoejbv
Supporter
Forum|alt.badge.img+16
  • Author
  • Supporter
  • Nov 3, 2026 3:08 PM UTC

Thank you for the pointers. We have done this upgrade in our test environment, and we have WAF controlled traffic. We have had some issues with the WAF settings in earlier setups, but with different outcome from this (REST error messges). We’ll check with our network tech team if this .


j.botterill
Evangelist
Forum|alt.badge.img+69
  • Evangelist
  • Nov 9, 2026 12:53 PM UTC

review the workspaces themselves, particularly the User Parameters used by the app. Parameters of type File, Folder, File/Folder, or URL can be configured to restrict what users are allowed to upload. For example, a File user parameter may be set to only accept specific file extensions such as .csv, .xlsx, or .zip.

If these filters were modified, interpreted differently after the upgrade, or are no longer aligned with the files being uploaded, some files may be rejected while others are accepted. Verify:

  • The parameter type being used (File, Folder, File/Folder, URL).
  • Any allowed file extension filters configured on the parameter.
  • Whether multiple file types are expected but only a subset is permitted.
  • Any custom validation logic within the workspace that checks filenames, extensions, or paths.

Also compare the workspace and published parameter settings between the pre-upgrade and post-upgrade environments to identify any differences that may be affecting upload behaviour.

Since the issue only affects certain files, the most likely cause is a validation rule or file-type restriction rather than a general problem with the app or Flow installation.


chadprop
Contributor
Forum|alt.badge.img+4
  • Contributor
  • Nov 19, 2026 9:08 PM UTC

I have a set of workspace apps on our Flow to convert data between file formats. After upgrading our installation in test, I experience some strange behaviour: While uploading data to convert, some files are accekted, while others are rejected. 

 

Looking into the network data using the developer tools, I find that the accepted files gives a response like this:

{"serviceResponse": {
"statusInfo": {"status": "success"},
"session": "3cc570c6-2d66-4d66-86af-22c6a2f56696",
"files": {
"path": "",
"file": [
{
"size": 1531,
"name": "file name.kof"
}
],
"folder": [{"name": ""}]
}
}}

The rejected files gives this response:

<html>
<head>
<title>Request Rejected</title>
</head>
<body>
The requested URL was rejected. Please consult with your administrator.<br>
<br>
Your support ID is: 12358467762813340<br>
<br>
<a href='javascript:history.back();'>[Go Back]</a>
</body>
</html>

Have anyone experienced this? Any tips on what could be causing this? 

I see this on several workspaces with different input file formats

Hi,
I’ve got a very similar problem on both our Flow Test and Prod instances.
After building several test workbenches that have a user parameter to upload files to a very simple feature reader.  I’ve tried KML, GPX, and CSV formats thus far.

The peculiar bit is that I can upload just about any file using the ‘browse file system’, but only for a source file of 10kb or smaller.  I can upload a 7 kb csv file, no problems.

As soon as I switch to one greater than 10kb, I get a “500 Internal Server Error” response to the POST request (using the browser developer tools).

All of these functions were working fine prior to a recent upgrade to 2026.3.1.1
The prior version we had was 2026.1.

I’m curious if this is a build issue or an underlying IT infrastructure incompatibility, as in is there something the IT department needs to alter or update to get things working again?

Cheers

Chad