Closed gjorgjevski closed 2 years ago
requests2 | where timestamp > datetime(2022-05-02T00:00:00Z) | where timestamp < datetime(2022-05-07T00:00:00Z) | where botId == "rio-test-6b4855a2-1baf-46f7-9116-0763ef351" | summarize total=count(), failedRequests=countif(resultCode startswith '5') by bin(timestamp, 60m) | render timechart
we only see few failed requests in that period caused by Redis call failures.
Hi @gjorgjevski , do you still repro the issue. We didn't see similar pattern in the bot service log data.
Seems it got resolved by itself. But i am more than sure that came from some changes in cloud. Thank you.
On Thu, Jun 9, 2022, 14:36 Jing Li @.***> wrote:
Hi @gjorgjevski https://github.com/gjorgjevski , do you still repro the issue. We didn't see similar pattern in the bot service log data.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/BotFramework-Services/issues/337#issuecomment-1151066187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AILHA5GG7M3M7FF62BH7JO3VOHQNPANCNFSM5VO5NHNA . You are receiving this because you were mentioned.Message ID: @.***>
Closed the issue for now. May reactivate this issue if we have proper repro steps to help the investigation.
Our backend project: .NET Core 3.1 Using Directline and Microsoft webchat.
Describe the bug
We are getting internal server error from Directline channel and its intermittent. There is no a specific case when you will get this error its just random and its happening. It can be for example if you call the same directline call for 10 times the error can happen 3 times. 3 of 10 .
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This internal server error should not be happening at all.
Screenshots