Search the message context properties through Message Box Data Monitoring
Suspended messages are routed to ESB and for some reason doesn't reach ESB, in this case user wants a notification
but problem is if you search in suspended messages there are too many and the suspended message application name does not reflect the application from which the message came - the application name of the suspended message is All.Expcetions
You need to go into the message context of suspended message & read the application name there.
Currently a powershell script is used to filter the applications in message context.
Basically can BizTalk360 go thru the message context and read the message application name as the suspended message application name is different
Eric Abts
shared this idea
-
Raheem Bauch
commented
Can BizTalk360 read the application name from a suspended message's context, even if it differs from the stated application? Yes, it should be able to! I've used similar tools to extract specific data from message contexts before, even when the high-level application designation was misleading. https://fivenightsatfreddysgame.io/
-
Anne Hathaway
commented
Interesting point! Custom messages for file processing failures are crucial for user-friendliness. Current critical errors are too technical. Instead of "failed message on configured port," something like, "No files found. Contact support if needed" would be ideal. This clarity enhances user experience, preventing unnecessary panic. Think of it as steering clear of confusion, like skillfully navigating a difficult level of Drift Boss.https://driftboss.lol
-
Flora Campbell
commented
Good point! Thanks for sharing feedback. Check out for more information: https://poor-bunny.org