Skip to main content

When I go to publish my workflow from form to flow I get this error: 

However when I go to run it on flow, I get an error saying that it doesn’t exist: 

58	2025-9-23 12:18:08 | ArcGISFeatureServiceReader: Connection 'connectionname' does not exist. Check connection parameter and connection definitions in FME options and try again
59	2025-9-23 12:18:08 | Python Exception <NamedConnectionNotFound>: FMEException: 1: ArcGISFeatureServiceReader: Connection 'connectionname' does not exist. Check connection parameter and connection definitions in FME options and try again
60	2025-9-23 12:18:08 | An error has occurred. Check the logfile above for details
61	2025-9-23 12:18:08 | The below feature caused the translation to be terminated
77	2025-9-23 12:18:08 | FeatureReader_2_<Rejected> (TeeFactory): FeatureReader_2_<Rejected>: Termination Message: 'FeatureReader_2 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Log and Troubleshoot > 'Rejected Feature Handling' to 'Continue Translation''

Here’s how I have the transformer in question set-up: 

 

I’m using FME Form/Flow 2025.1.1 using the Esri ArcGIS Feature Service reader in a feature reader. 

Is it that the connection exists but isn’t the right sort of connection?

 

i.e. it was previously a portal connection and looking at your screenshots you’re now using an Esri ArcGIS Feature Service Reader which uses a different sort of connection

I was using the new connection for the Esri ArcGIS Feature Service Reader, and that was the connection my web app was not able to use. A coworker was able to help me through some troubleshooting steps. First we used the run a workspace function to determine if it was an issue with flow or the FME Web App. Once we determined it was the App, we edited the App’s Token Permissions, which was not something I knew you could do. 

If you click on your user icon in the top right of flow and select Manage Tokens, you will get to a screen where you can pick your workspace. Then under the permissions “connections” section make sure the new connection  has run permissions, and click save. Then retry running the web app and it should hopefully run, at least this is what worked for me. 

 

Community Stats

32,026
Posts
121,627
Replies
39,647
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.