When creating an automation and attempting to save it, i’m getting an ‘You are forbidden error’ with the same superuser account

Hi ​@sapplezyw,
A few questions to help understand the case a bit better:
 

Are you seeing this issue for all workspaces or specific workspaces in certain repositories on Flow?

You mentioned that you are publishing as superuser. Is it FME Flow's default superuser account or another superuser account? On the User Permissions in the Web UI, if you look at the user, do they have publish permissions to the repositories?

Is this a system user or an AD/LDAP/SAML imported user ? Are you able to manually login to the FME FLow Web UI directly as that user ?

Hi ​@donalmateer ,
Thank you for the reply - To answer your questions:

• I’m seeing it for all workspaces in all repositories
• It’s another user that has been given superuser role
• Yes I have also given publishing rights on all repositories
• The user is a system user
• Yes I can manually login and upload/replace workbenches through the flow interface without issue

When I try to save an existing automation that I own, I see a small ‘You are forbidden’ badge. This does not effect my ability to save the automation. 

I also tried creating a new user with superuser permissions but that had the same issue. We also attempted to setting the WAF policy in Azure for "Inspect Request Body", to False. That did not work either - We got this idea from someone having a similar issue 
 

Did you read this thread at all?

 

Theres a comment at the bottom using FME 2025.1. could be related. Although that would usually effect all users of FME Flow.

One clue might come if you open up you browser developer tab when trying saving your automation. clicking the save button will cause a series of calls from the client to the server, possibly one of these calls is failing.

Have you tired restarting you FME Flow?

Thanks ​@virtualcitymatt, I tried to save the automation with developer tools and I can see a 403 error related to Microsoft azure application gateway. I’ll try and do some testing with out cloud engineers to track the setting we need to change: