I am using IDialogContext.PostAsync("[SOME STRING]") to respond to end users from my bot application. The channel I am testing on is the SMS channel via Twilio. I have noticed that my application successfully executes the PostAsync call with no exception being thrown (wrapped it with try/catch), but the message is not being delivered consistently. The messages are lengthy and more than 1 segment.
Is the message length an issue from a connector perspective because those "dropped" messages don't even show up in my Twilio logs?
Is the connector service using some type of queuing mechanism as well and is failing transport to twilio.
Is there best practice example of handling transport or unhandled exceptions? Any specific bot example that may have good error handling code? Is there bot code extending some of the Web API 2 global error handling classes (https://docs.microsoft.com/en-us/aspnet/web-api/overview/error-handling/).
4) Should I be using a raw client and posting to the Connector API instead so that I can handle the HTTP responses I am receiving instead of the IDialogContext.PostAsync method?