microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
The resource has changed since the caller last read it; usually an eTag mismatch
Open
Nobody has claimed this yet.
Needs: Attention :wave:
Service issue
type:bug
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Describe the bug
I am trying to download a driveItem like so:
var driveItemContent = await Graph.Drives["asdf"].Items["zxcv"]
.Content
.GetAsync(cancellationToken: cancellationToken);
But for a particualr document I get a 409 error
Never seems to go away even if I re-do the request
Plz fix
Expected behavior
Gets the file, 409 can be handled internally by kiota
How to reproduce
var driveItemContent = await Graph.Drives["asdf"].Items["zxcv"]
.Content
.GetAsync(cancellationToken: cancellationToken);
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_Contributor guide
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 with the DriveItem content request shown in the issue and inspect how the SDK or Kiota handles a 409 eTag mismatch. Reproduce it with the provided drive, item, and cancellation-token call, then compare behavior for the affected document; done means the file download succeeds or the error is handled as expected.
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
- 30/100