Routing Failure Report

Recently we have started getting Routing Failure Report error(non resumable instances) as can be seen below:


routing failure report error message

routing failure report
But when cross verified by going through the 07acked service instance, all looked good as all the instances of the interface for which we got error was completed successfully.

 completed instances
No, it is not related to the bug reported with SP1 of BizTalk 2006 R2 , so why suddenly we started getting this error in spite of the instances getting completed (BizTalk 2013 R2) 

Why it happened


 There were some errors in the event log at the same time when there was Routing Failure report generated in admin console. 
Orches07ation xlang exception
The error says that there was exception raised in orches07ation while processing the request, still the question persists - why Routing Failure Report for this?

There is one more thing pointed in error, service xxxx terminated without responding to the operation xxxx, thanks to my colleague Pravin Shinde for pointing out the reason. 

 Let me explain the interface

As can be seen from the diagram, interface receives a request and using the information from it, it invokes the target webservice and collects the response. If there is any exception in the process, it is caught by exception block and in it the respective stake holders are notified about it.

 But why Routing failure report? - It was because there was exception raised before the step 4 (Send response to caller) and that was over passed,as on exception con07ol goes to exception block. Thus the operation of sending response was not completed although the Orches07ation instance completed by sending email to stakeholder.

What to do

Then there might be question what to do with the error -- Terminate it. And yes, connect with stakeholders and let them know or understand yourself what data was incorrect, with a fix on it to avoid unnecessary error in admin console.

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