Search

FME Flow Troubleshooting: Flow Apps

Matt Meeboer
Matt Meeboer
  • Updated

Full Guide: FME Flow Troubleshooting Guide

Is your FME Flow App not working as you intended? Are you seeing unexpected user-interface issues?  Please read below for some common troubleshooting tips, questions, and resources.

Content Overview

Initial Troubleshooting

  • If the app is not accessible, confirm that:
    • The app was saved and appears in the list of Flow Apps on FME Flow Web UI > Flow Apps > Manage <App type> Apps page
    • The app is active and hasn’t expired or been disabled
    • You are entering the correct URL to the app. The URL may change if your organization changes its FME Flow hostname
    • The FME Flow machine hosting the app is running
    • The FME Flow services are running on the machine hosting the app
    • You are on the same network as the FME Flow hosting the app. If the FME Flow is hosted on-premises behind a company firewall, you must be on the same company network, either directly or via VPN. The app will not be accessible via the internet in this scenario. 
  • If the app is still inaccessible, try checking your browser’s developer tools to see what errors are being returned. In Google Chrome, the developer tools are accessed by pressing F12. Refresh the app web pages after opening developer tools and check the Network tab for any errors that may indicate why the app isn’t accessible.     
  • If the app is accessible but returns ‘Failed’ when you run it:
    • There are many Log Files that may help identify job-related errors. Start by checking those listed below.
      • <FMEFlowSystemShare>\resources\logs\core\current\fmeserver.log
      • <FMEFlowSystemShare>\resources\logs\core\current\fmesharedresource.log
      • <FMEFlowSystemShare>\resources\logs\engine\current\*.log
  • Currently, in Automation Apps in FME 2022.2, the File manual parameter does not support temporary uploads. The File parameter allows end users to select a file from the FME Flow Resources folder.

Common Issues

“User Parameters are missing from my app’s form.”

In your Flow App settings, expand the Parameters section and confirm that “Show in App” is checked. If the parameter is not in the Parameter section at all, confirm it exists in your workspace and that it is a published parameter.

“My app has a file/URL parameter that is visible, but users don’t have the option to upload files. They can only browse for resources on FME Flow.” 

In your Flow App settings, ensure the setting “User Can Upload” is enabled.

“I receive the error "There was and error uploading the file" when trying to upload files via my app”

Check your dataupload.log file found in resources\logs\service\current for errors. An EOFException error, as shown below, could indicate an incorrectly configured load balancer in a fault-tolerant installation. Ensure that the load balancer is routing traffic to all FME Flow instances in the fault-tolerant installation and not pointing to itself. Please see Installing for Fault Tolerance for more information.

Request failure, status 400, org.apache.commons.fileupload.FileUploadException: java.io.EOFException
“Why are users being asked to log in? What credentials are they supposed to enter?”

If “Require Authentication” is enabled, users will be prompted to log in when accessing the app URL. Ensure the necessary users and/or roles have been allowed access to the app. Users log in with the same method and credentials they use to log on to FME Flow. For example, their FME Flow username and password.

“I cannot grant an Active Directory (AD) group access to my app.”

This is a known issue. Each AD user needs to be added individually.

“I get an “Unauthorized request by user due to lack of proper permissions” error when I run my app.”

If your app uses a database or web connections, the user running the app must have access to them. Please read FME Flow Connections Runtime Error: Unauthorized request by user due to lack of proper permissions for more information.

“When configuring an FME Flow App, the Show In App checkbox is missing for all parameters that are within a group box.”

This is a known issue. Move the File parameters outside of the group box.

"I receive an "Unhandled Exception" error when trying to save my FME Flow App."

This is a known issue that can occur when an optional parameter has no default value. FME Flow may let you save the app with no default value once or twice before the error occurs. Try recreating the parameter or providing a default value.

" I created a file manual parameter for my Automation app and the end user can't access the FME Flow Resources folder to select a file." 

This is a known issue with the Automation app token lacking permissions and is resolved in FME 2023.0 and newer. The workaround is to go to the Token Management page and grant Access and List permissions to the Resources' subfolders of choice. For example, the Data folder or a Network directory.

"Jobs do not route to the correct queue when the rule is based on user role"

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

Are you still experiencing issues? 

Please consider posting to the FME Community Q&A if you are still experiencing issues that are not addressed in this article. There are also different support channels available.

Have ideas on how to improve this? 

You can add ideas or product suggestions to our Ideas Exchange.

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.