Issue
While working on a POC about Debatching in Logic Apps using SplitOn, I was encountered with an below error when tried to add Response action in the workflow

"Failed to save logic app DebatchXMLUsingSplitON. The workflow with
'Response' action type should not have triggers with 'splitOn' property
defined: 'manual'."
'Response' action type should not have triggers with 'splitOn' property
defined: 'manual'."
Why it happened
As I had to debatch an xml message, following xpath expression was provided to splitOn property
So this property will make logic app to instantiate equivalent number of the instances
as that of number of splitted message.
Say, a batched message with 3 messages in it is posted to this Logic App, then 3 instances
of logic app gets created.
And this is the reason, why designer stops us when we try to add Response action -
because incoming HTTPS requests state is no more preserved(connection gets closed), as new instances gets
created thus ending the session.
xpath(xml(triggerBody()),'//*[local-name()="PurchaseOrder" and namespace-uri()
="http://www.adventure-works.com"]')
So this property will make logic app to instantiate equivalent number of the instances
as that of number of splitted message.
Say, a batched message with 3 messages in it is posted to this Logic App, then 3 instances
of logic app gets created.
And this is the reason, why designer stops us when we try to add Response action -
because incoming HTTPS requests state is no more preserved(connection gets closed), as new instances gets
created thus ending the session.
What to do
Remove the Response action and save it :)
If you have questions or suggestions, feel free to do in comments section below !!!
Do share if you find this helpful .......
Knowledge Sharing is Caring !!!!!!
Learn More about some more Logic App errors
- The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used
- Selected file must be between 1 and 2097152 bytes
- SplitOn property doesn't validate expression at design time
- The template language function 'xpath' expects its first parameter to be an XML object
- The template language expression 'xxx' cannot be evaluated because property 'xxx' doesn't exist. Property selection is not supported on content of type 'application/xml'