microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Bot occasionally unable to join with internal error

Open
#532 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
Occasionally, the bot goes into a sort of failed state where it is unable to join the calls with an internal error with diagnostic code 500#7117

error logs:
Publish to recordingbotevents subject CallTerminated message Call.ID a71f5d00-4f80-4cda-9276-8512e98056c1 Sender.Id a71f5d00-4f80-4cda-9276-8512e98056c1 status updated to Terminated - Server Internal Error. DiagCode: 500#7117.@

Is this due to something on our end or is it due to general instability of the teams bot application?

Expected behavior
Bot is supposed to join the call normally.

Graph SDK (please complete the following information):
Microsoft.Graph - 3.8.0 (nuget)
Microsoft.Graph.Communications.Calls - 1.2.0.850 (nuget)

Call ID
a71f5d00-4f80-4cda-9276-8512e98056c1

Mon, 04 Apr 2022 21:47:17 GMT

Additional context
Bot is deployed to kubernetes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reported error log, diagnostic code 500#7117, Microsoft.Graph 3.8.0, Microsoft.Graph.Communications.Calls 1.2.0.850, and the Kubernetes deployment context. The issue names no repository file, test, or reproducible trigger; done would require identifying whether the failure is in the deployment or the Teams bot service and documenting or fixing the cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.