An activatable receive must be the first executable statement in a service



Whenever we add the Orches07ation to a project, the first thing which is done almost every time is to add Receive shape as the first shape.  That’s because we need to apply some process when some particular piece of info (message) is obtained. Thus initiating the process designed in the orches07ation.

Well this raised a question, can’t other shapes be used as the first shape in Orches07ation?
To find out, I added a loop shape as a first shape with a Receive shape within it. Logically it seemed correct as I want to receive messages until the loop condition is satisfied.



When clicked on build following error appeared





With all said it’s obvious to think that  the first shape has to be Receive Shape . Well there are exceptions, shapes  like Group shape, Scope Shape, Listen Shape, Parallel shape  and orches07ations configured with parameters to enable invocation from other orches07ation.



Will keep sharing as and when find something!!!!! Happy New year to all !!!!!!!

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