web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Request failed with st...
Power Automate
Answered

Request failed with status code 400 error on power automate for run only users

(1) ShareShare
ReportReport
Posted on by 11
When i am trying to add users into Run-Only Users, I am getting the error - Request failed with status code 400 error. What is the reason for the same & how to solve it.
Also, I have another case where in a managed solution when i add run only users, a unmanaged layer is being created automatically to the managed solution.
Kindly help to solve
Error.png
image (3).png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:
I have the same question (0)
  • Verified answer
    Nafiun2120 Profile Picture
    144 on at

    Here are some steps and checks that can help resolve the issue:


    1. Check Permissions: Ensure that the user you're adding has appropriate permissions. They should have at least the Environment Maker or System Administrator role. If you're adding the user to a specific flow, ensure they also have the right permissions in the flow's environment.

    2. Check Licensing:Confirm that the user has a proper Power Automate license (e.g., Power Automate per user or per flow). Without proper licensing, users might not be able to be added as "Run-Only Users."

    3. Managed Solution & Unmanaged Layer: The creation of an unmanaged layer when adding run-only users in a managed solution is a known behavior. To avoid this, consider checking the version of the solution. If possible, work in a solution context where the unmanaged layer won't interfere.

    4. Review the API Request: If you’re using an API to add users programmatically, ensure the request body and headers are properly formatted. A 400 error often indicates an issue with the request. Double-check the API documentation to ensure the request is structured correctly.

    5. Lock Solutions for Deployment: If you're working with a managed solution, avoid making changes directly to the solution while adding Run-Only Users. This could trigger the creation of the unmanaged layer. Instead, make sure the solution is locked for deployment and only add users manually via the Power Automate interface if necessary.

    6. Do like the post so that others may benefit as well from this post, and do mark it as such if I could solve your problem.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 594

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 281 Super User 2026 Season 1

Last 30 days Overall leaderboard