Unable to upload csv file to workspace

Does this pop up as soon as you load the workspace?

I’d open up developer tools and see if there is a specific network call that is failing. This should help narrow down what the issue is.

It may also be worth checking the log files for any entries that align with when you load up the workspace.

Hi ​@tp_atkins , 
 

You need to check some of this causes:

1. The path or resource to the CSV file is no longer available
   (e.g., the file was deleted from the Resources folder, or the resource name has changed).

2.  The workspace expects a parameter that is not being passed
   (someone might have accidentally changed the parameter name in the .fmw file).

3.  The FME Flow 2025.1 update may have changed how file uploads are handled in the web form
   (there have been known changes to the upload mechanism in newer versions).

4.  Permissions issue — the service account running FME may no longer have access to the file location (if the CSV is read directly from disk).

Hi ​@hkingsbury  thanks for your response.

No the error only comes when I click the ‘browse the file system’ button and point to the csv file, which is just 1kb. 

There aren’t anything seen in the logs (resources/core/current) about any errors when the workspace loads. Also there are many other workspaces which all works fine, except this upload one.

One thing noticed is that within the services section, the URL is https://domain-name.com/fmedataupload where as when the file upload request is looked via dev tools, it is: https://domain-name.com/fmeserver/dataupload/NextGen/CreateAttachmentsTableAndView.fmw/

it is referring to dataupload not fmedataupload.

Nothing has changed since migrated from fmeserver to fmeflow, and we successfully ran this workspace as recent as 25/10/2025.

It is also noticed that same behaviour in a totally different instance where also this specific workspace was tested working before, but not anymore.

Thanks for your help

Thomas

Hi ​@hkingsbury I got your question not properly understood, and apology for it.

Having looked at the calls in dev tools, it appears that as soon as the workspace is loaded, the error comes. I have quite few workspaces in the repository and this is the only one which throws error when loaded.

Given that this worked before in this instance and a totally independent, but similar deployment, I wonder what has changed.

Tried to republish the workspace but the issue remains.

Thomas