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 / The flow stops running...
Power Automate
Answered

The flow stops running (conflict with business rule)

(0) ShareShare
ReportReport
Posted on by 10

Hi, 

 

I have 2 environments and when a record is created in Env 1 I want the flow to copy it to Env 2 but also I want to prevent users to add a record manually in Env 2.

 

I have added a business rule to show error and prevent the user to create records in Env 2.  But now the flow is conflicting with this business rule. 

 

Is there a way around this issue?

 

Thank you!

Categories:
I have the same question (0)
  • Verified answer
    Rodrigo Hentz Profile Picture
    Microsoft Employee on at

    HI @prajwal-bhetwal how are you?

     

    I think you can deactivate the business rule in environment 2 and to prevent users to create records change the security role associated to the users and do not add create privileges for this entity. 

     

    Only left permission for the user that is used on flow to create the record.

     

    Let me share an article about security roles and privileges Security roles and privileges - Power Platform | Microsoft Docs

     

    Best regards

     

    Rodrigo Hentz

    Microsoft Power Platform Support Engineer

     

     

  • Prajwal Bhetwal Profile Picture
    10 on at

    Hi Rodrigo, 

     

    Thanks for your response. It has to be done for only one of the contact types. Not based on user. If contact type = B, then prevent any user from creating the record. 

  • Verified answer
    Rodrigo Hentz Profile Picture
    Microsoft Employee on at

    Hi @prajwal-bhetwal thanks for the reply. 

     

    With this new condition, I think that an attribute can be used to identity if the user is creating the record or your flow. And at the business rule check the content of this attribute. Do not forget to add this attribute on form, that way business rule will work.

     

    Validation in a plug-in could be an alternative too. Check the user context. If the context user is not the flow user, thrown an exception.

     

    Best regards

     

    Rodrigo Hentz

    Microsoft Power Platform Support Engineer

     

     

     

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!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 60 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 54

#3
Expiscornovus Profile Picture

Expiscornovus 47 Most Valuable Professional

Last 30 days Overall leaderboard