Updating resource subscription to presence results in: Operation: Update; Exception: [A task was canceled.]

[ROMICO-GmbH]

Describe the bug

Sometimes when updating subscription to resource of teams presence we get response:
Microsoft.Graph.Models.ODataErrors.ODataError: Operation: Update; Exception: [A task was canceled.]

This happens once or twice a day. Requests in those incidents seem to be taking from 20 sec to 60 sec. Normally it is ~1sec.
Subscription refresh is triggered by lifetime route.

This results in no presence changed event coming to us before another of lifetime event comes in (which happens after 40-60 minutes lates).

Expected behavior

Presence subscription should be refreshed without throwing error.

How to reproduce

Create subscription to presence resource and refresh it when hit by subscription lifetime event.
Subscription is made this way with delegate connection client:

var subscriptionModel = new Subscription
{
    ExpirationDateTime = DateTimeOffset.UtcNow.AddHours(1)
};
await client.Subscriptions[subscriptionId].PatchAsync(subscriptionModel);

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_

[andrueastman]

Thanks for raising this @ROMICO-GmbH

Are you able to capture other properties in the error like the status code? https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/main/docs/errors.md#checking-the-error-status-code

As you are getting an exception of ODataError this suggests that the error here was deserialized from a response from the API suggesting a API side error and not the SDK timing out waiting for the response. One possibility it catching the error and handling it by retrying the request depending on the status the API returns.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.