The best way I have found to debug correlation is to use the admin console to run a query for all subscriptions. When your orchestration dehydrates to wait for the MDN, it should create an instance subscription based on the values on the correlation set. You can view these values and the exact filter expression using the admin console. When the MDN arrives, it should be suspended due to no subscribers found, and you should be able to check all of the context properties against the subscription.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name