Apps failing due to permissions issues FME Flow 2025.2.4 Build 25835

Hi ​@gboquin,

Flow apps authenticate with tokens in 2025.2.4, so the final section of the article you sent is relevant. Creating roles and sharing connections with them shouldn’t be required for this use case.

To get your app working:

1. Locate the token in Token Management - it should have been created automatically alongside the App.
2. Open the token. Under Connections, grant Access to the required connection. 
3. Save the token, and try run the App again.

If you’re having permissions issues, I recommend trying to create a new workspace app and using all of the default settings - permissions should be applied to the token automatically depending on its dependencies. 

Let me know if you have any questions about this!

​@zoe.forbes Thanks for your reply. I greatly appreciate it.  The part that I don’t get is why do I need the token? I am not sharing it with a third party tool.

Hi ​@gboquin,

In your version of Flow, I believe API tokens are used for Workspace Apps since they’re sometimes public. A public workspace app is essentially a front-end wrapper for a service webhook (such as /fmedatastreaming), and authentication is performed in a very similar way for both. Private workspace apps are the same, but are login-gated.

In saying that, it’s rare that permissions should need to be assigned manually, since dependencies should be automatically detected upon creation.

Workspace app authentication has been changed in 2026.1 however - API tokens have been replaced with temporary session tokens. Permissions can’t be assigned manually to these from the Manage Token page.

Hopefully this clarifies things - please let me know if not.