I use IDialogContext.PostAsync("[SOME STRING]")to respond to end users from my bot application. The channel I'm testing is an SMS channel through Twilio. I noticed that my application successfully makes a call PostAsyncwithout exception (terminates it with try/catch), but the message is not delivered sequentially. Messages are long and more than 1 segment.
Is message length a problem from the point of view of the connector because these “discarded” messages do not even appear in my Twilio logs?
Whether the connector service also uses some kind of queuing mechanism and does not migrate transport to twilio.
Is there a better example of handling transport or unhandled exceptions? Any concrete bot example that might have good error handling code? Is there a bot code extending some of the global API 2 error handling classes ( https://docs.microsoft.com/en-us/aspnet/web-api/overview/error-handling/ ).
4) Should I use a raw client and send it to the connector API so that I can handle the HTTP responses that I receive instead of the method IDialogContext.PostAsync?
source
share