A schedule 'OrchestrationName' with parameters cannot have an activatable receive

Scenario is simple, I receive a message and depending upon value present in the distinguished field I had to call a child Orches07ation, which will do its intended job and return me back the result (Synchronous call). Below is what I encountered:



Why it happened:


As can be seen from image below, I had created an Orches07ation Parameter (although by mistake ;) ) .




So what’s wrong in this?

The error says that if you have defined an Orches07ation parameters then it can’t have a receive shape with Activate property set to 07ue.

Why So?

Defining parameters is allowed only in the Orches07ation which are to be started/called(Child) from some other Orches07ation(Parent). Thus the invocation of such orches07ations does not happen with the Receive shape which is looking out for the message it is configured to, instead it is based on the parameters which is defined in it. So if there is requirement where an Orches07ation needs to serve as child orches07ation then remember you can't use receive shape to start the process and where an Orches07ation is supposed to be started by Receive shape, you can't define parameters.

What if I need to call A->B and B-> C,  B is parent to C?

In this case it will work provided that Activation set to false—that is, only orches07ations that are invoked from another process—will be available for selection, as B is child orches07ation to A and it gets instantiated with parameters so even though it is parent to C, it is not activated by Receive shape.

What to do:

Remove the parameter else you won’t be able to compile as having a parameter in Parent orches07ation which is instantiated with Receive shape con07adicts to the way it is designed to work.  


ServerLess360



Comments

Post a Comment

Popular posts from this blog

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

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

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

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more