I have been managing a bot for a couple months now, and I recently ran into an issue where Facebook is having intermittent issues connecting with the Bot Connector. While in dialog with Facebook, we're seeing that at random, some messages get through to the Facebook chat client while others return as 500s. This ranges from sending a generic typing message to responses generated from a FormFlow dialog.
The exception raised:
System.UnauthorizedAccessException: Authorization for Microsoft App ID 4b6154c8-3228-4403-8999-dc7ae63c7d5c failed with status code Forbidden
at Microsoft.Bot.Connector.JwtTokenRefresher.<SendAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Bot.Connector.Conversations.<ReplyToActivityWithHttpMessagesAsync>d__7.MoveNext()
Our slack channel is still functioning as expected.
I did a run through of #1105 which included:
My current project setup is:
One of our calls that generate this error:
Activity reply = activity.CreateReply();
reply.Type = ActivityTypes.Typing;
reply.Text = null;
await connector.Conversations.ReplyToActivityAsync(reply);
Confirm problem with Facebook.

it's the same for me as well
i can reproduce the same issues with EchoBot from the sample project of BotBuilder, some messages get through but some messages return 500 with UnauthorizedAccessException. Is there any workaround for now? as it's just stop the bot working.
Having the same issue as wiltodelta
I'm seeing this on Node.js as well, some messages go through and some are 403. After testing it on Facebook and Skype, only the Facebook channel has the problem.
@wiltodelta there's an open issue #1254
Please comment something there to show Microsoft's team that's a general problem.
Hi folks, we're looking into it. Thanks
Verifying on my side that I think this issue has been resolved along with #1254 and #1257.
Thank you for the quick response!
Most helpful comment
Hi folks, we're looking into it. Thanks