Search

FME Flow Troubleshooting: REST API

Liz Sanderson
Liz Sanderson
  • Updated

Full Guide: FME Flow Troubleshooting Guide

Are you encountering issues accessing or invoking the FME Flow (formerly FME Server) REST API? Please read below for some common troubleshooting tips, questions and resources.

In 2023, FME Server underwent a name change and is now known as FME Flow. Since this article discusses features present in previous versions of FME, it will refer to both names interchangeably, using the appropriate product name based on the year the feature was introduced. For more information on the rebranding, see our website. 
 

Content Overview

 

Initial Troubleshooting

  • Are you able to access the main http(s)://<hostname>:<port>/fmeserver page? If not, this may be a symptom of a larger issue.
  • Log Files that may help identify errors include both FME Flow and Tomcat – these can be accessed via file system. 
<FMEFlowSystemShare>\resources\logs\core\current\fmeserver.log
<FMEFlowSystemShare>\resources\logs\tomcat\catalina.log
  • Can you try using a different web browser? You may also consider testing in a private window or emptying the cache or deleting cookies.

 Are you seeing this error in the FME Flow UI? “There was a problem communicating with the REST API”
image.png

If so, view the developer tools to see if there are any errors. To do this follow the steps below:
  • Right-click and select inspect
  • In the side panel go to the Network Tab
  • Refresh the page
  • See if there are any errors
image.png


If you do create a support case please download the HAR file and attach it to the case.
image.png


​​​​ Are you trying to access the FME Flow REST API in an HTTP call?
If so, try the following tips:
  • What version of the REST API are you using? Try using the latest version.
  • Are you receiving any response codes? You can cross-reference error codes with the REST API documentation.
  • Are you using a valid token? And does it have proper permissions for the component(s) you are accessing via REST? Try creating a token with all permissions to test.
 

Common Issues

“My FME Flow Token has changed or Expired”
It’s possible for tokens to expire and this would cause REST API calls that once succeeded to fail. To find out how to manage tokens in FME Flow see Token Management in FME Flow. 
 
“REST API V1 no longer works”

As of 2020.0 the REST API V1 has been removed from FME Server. REST V2 has also been deprecated and is no longer being worked on, but is still in FME Server in 2020. If you are planning on upgrading your FME Server is it highly recommended that you take the time to update any REST V1 or V2 calls. Please have a look at our Migration From REST API V2 documentation if you need a hand updating your calls.  

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?

Comments

0 comments

Please sign in to leave a comment.