Subscribing to presence for multiple users

[tcs-devel]

Hi,

we are about to implement presence subscriptions using the BETA SDK (v0.32.-preview). During that some issues and questions came up which would require clarification. As we did not find the information in the documentation we opened an SO question - sadly without real useful answers yet. That's why we are trying our luck here, maybe someone can bring light into the darkness. Here the information from the SO question:

---

Everything is working smoothly when just subscribing for some users. As soon as the number of users gets larger, problems are starting. Basically we are doing it like mentioned here:

Subscription = Client.Subscriptions.Request().AddAsync(new Subscription
{
   Resource = $"/communications/presences?$filter=id in ('<guid>','<guid>',...))",
   ChangeType = "updated",
   ...
}).Result

Issue 1: Two subscriptions, one user/presence on each

After everything was working, we tried to create multiple subscriptions. In our test case two subscriptions with a single contact on each. Trying to create a second subscription does not work with the error "Operation: Create; Exception: [Status Code: Conflict; Reason: A subscription already exists. It must be deleted before a another can be made.]"

• We am now wondering whether we are doing something wrong or if this is a limitation (haven't found anything in the docs)? ...We hope we are doing something wrong as the goal would be to monitor even more then the 650 users mentioned in the linked article above :). The error we get:

  Code: ExtensionError
  Message: Operation: Create; Exception: [Status Code: Conflict; Reason: A subscripton already exists. It must be deleted before a another can be made.]
  Inner error:
  AdditionalData:
  date: 2020-11-08T20:47:37
  request-id: 9d45a16b-9cac-4515-92f9-b81b36318189
  client-request-id: 9d45a16b-9cac-4515-92f9-b81b36318189
  ClientRequestId: 9d45a16b-9cac-4515-92f9-b81b36318189

Issue 2: One subscription, multiple users/presences

Afterwards we tried to create a single subscription with more than our three test users, which sadly did also not work as expected:

• 250 Users/presences

  Code: ExtensionError
  Message: Operation: Create; Exception: [A task was canceled.]
  Inner error:
  AdditionalData:
  date: 2020-11-08T20:38:30
  request-id: c6398df3-c856-4f80-9495-0b76714d9592
  client-request-id: c6398df3-c856-4f80-9495-0b76714d9592
  ClientRequestId: c6398df3-c856-4f80-9495-0b76714d9592

  • 350 Users/presences

    Code: ExtensionError
    Message: Operation: Create; Exception: [Status Code: BadRequest; Reason: ]
    Inner error:
    AdditionalData:
    date: 2020-11-08T20:40:45
    request-id: 297f7b7d-e2d7-4ad4-8083-cc4797415287
    client-request-id: 297f7b7d-e2d7-4ad4-8083-cc4797415287
    ClientRequestId: 297f7b7d-e2d7-4ad4-8083-cc4797415287

  • 650 Users/presences

    Code: UnknownError
    Message: The page was not displayed because the request entity is too large.
    Inner error:
    AdditionalData:
    date: 2020-11-08T20:35:28
    request-id: b3580f44-dcec-4fdc-87e2-50ae92da8bd3
    client-request-id: b3580f44-dcec-4fdc-87e2-50ae92da8bd3
    ClientRequestId: b3580f44-dcec-4fdc-87e2-50ae92da8bd3

Any information would be helpful. Thanks in advance.

AB#7145

[MIchaelMainer]

@jsandoval-msft Can you take a look at this?

[tcs-devel]

Any updates on this?

[andrueastman]

Ping @jsandoval-msft

[kafka-yu]

Hi Team,

any update on this? We meet same issues like above #1 #2.

[Rashad-j]

Is this solved? we still have a problem here

[petrhollayms]

Thank you for reporting this issue. This appears to be an issue or limitation with the service APIs. Unfortunately, as the Microsoft Graph SDK team, we do not have ownership of the APIs that are causing you issues. We invite you to create a question about the service API to Microsoft Q&A and tagged with one of the [microsoft-graph-*] tags, that way it will get routed to the appropriate team for them to triage:

https://aka.ms/msgraphsupport or directly https://aka.ms/askgraph

For now, we will close the issue on our side but feel free to open it in the relevant repository if you think the issue is specific to SDK. Please let us know if this helps!

Note: We will close this repository on April 19, 2024.