microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Graph Issue
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
TenantId: Case needs to be raised from the tenant affected by the reported issue : dc128099-4393-4da2-955c-8bf536113f0d
Application Id/Client Id: bf8608f9-a733-41ba-9dac-e38d5b46ee13
Graph API used with the Request Body: Microsoft.Graph.Communications.Common.Transport.GraphHttpClient
Method: GET/POST/PATCH/DELETE/PUT: POST
Permission Type: Application permission or Delegated permission?: Application Permission
API Version: v1 or /beta: For beta version, please report the issue at: https://aka.ms/askGraph
Graph SDK: If the issue started with version change, please report in the GitHub project
request-id: We don’t have the request-id, bit we have the scenario-id if this is useful for you. (ScenarioId: 4599cc7d-1a55-4801-980c-a025a1e5177a)
client-request-id: Please provide all the Response Headers
StackTrace: at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.d__42.MoveNext() at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.SendHttpRequestAsync[T1,T2](IGraphRequest1 graphRequest, CancellationToken cancellationToken) at Microsoft.Graph.Communications.Common.Transport.GraphHttpClient.SendAsync[T1,T2](IGraphRequest1 graphRequest, CancellationToken cancellationToken)
at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.d__12`1.MoveNext()
$>2025-01-31T20:59:11.3799853Z Info: CommunicationsClientExtensions.cs:156 LogAndCreateResponse
10: timestamp: Please provide the time when the query was last run, no earlier than 1 week prior
2025-01-31T20:59:11
11: HTTP Status Code:
"code": 408, "message": "Callee could not be reached.", "subcode": 8544
Caught an Exception running the task: Answering call ...
exception: Code: generalException
Message: Unexpected exception returned from the service.
12: Error Message if any: Message: Unexpected exception returned from the service.
Scenario Id: 4599cc7d-1a55-4801-980c-a025a1e5177a
Method not found: 'Void Microsoft.Graph.Communications.Common.Transport.GraphHttpClient.LogResponse(System.Diagnostics.TraceLevel, System.Net.Http.HttpRequestMessage, Int64, System.Net.Http.HttpResponseMessage, System.Object, System.Exception, System.String, System.String, Int32)'.
StackTrace: at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.d__42.MoveNext() at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.Start[TStateMachine](TStateMachine& stateMachine)
at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.SendHttpRequestAsync[T1,T2](IGraphRequest1 graphRequest, CancellationToken cancellationToken) at Microsoft.Graph.Communications.Common.Transport.GraphHttpClient.SendAsync[T1,T2](IGraphRequest1 graphRequest, CancellationToken cancellationToken)
at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.d__12`1.MoveNext()
$>2025-01-31T20:59:11.3799853Z Info: CommunicationsClientExtensions.cs:156 LogAndCreateResponse
ScenarioId: 4599cc7d-1a55-4801-980c-a025a1e5177a
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing GraphAuthClient.SendHttpRequestAsync, GraphHttpClient, and CommunicationsClientExtensions.cs:156, then reproduce the POST failure using the supplied scenario ID and timestamp. Done means identifying whether the missing LogResponse method is caused by an incompatible dependency or service response, and documenting a confirmed resolution or reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100