Property value is not valid : A non-transactional Orchestration cannot contain any other Transactions

It was during building the project which has Atomic scope, following popped up.





Why it happened: 

It is the orches07ation designer which is designed to validate the properties against the shapes used. If any of the properties violate or are not as per the validation rule then notification is raised while building the project as "Property value is not valid."  It is common for all shapes but to know the exact reason we need to see in the details - it tells what went wrong.



What to do :


1. Orches07ation itself should be set as Long Running.
2. For this click on the white space and set the Transaction Type to Long Running.

In this scenario, it was the usage of Atomic scope in non-07ansactional orches07ation. You can only set a scope to have a 07ansaction type other than None if the orches07ation itself is a long-running 07ansaction.

So it is kind of mandatory to mark orches07ation as long running if Atomic scope is to be used.

ServerLess360



Comments

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Getting Started with Logic Apps - AS2

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin