We have created a subscription for users and its worked fine for us but currently, we are facing an unexpected issue related to getting a subscription because want to delete the previous subscription and create a new one for deletion we need a subscription id and get a subscription is not working let me share screenshots
subscription is already created I need a subscription list and get subscription list is not working
response is empty : "value": []
@CarlZhao-MSFT subscription is exist but the list of subscriptions is empty when I call https://graph.microsoft.com/v1.0/subscriptions API a few days earlier its worked fine but now it's not working
I need the list of created subscriptions
https://graph.microsoft.com/v1.0/subscriptions
"error": {
"code": "ExtensionError",
"message": "Operation: Create; Exception: [Status Code: Conflict; Reason: A subscripton already exists. It must be deleted before a another can be made.]",
"innerError": {
"date": "2022-01-25T09:07:22",
"request-id": "6a7df85b-0b69-4b4c-97de-da4b8839437c",
"client-request-id": "6a7df85b-0b69-4b4c-97de-da4b8839437c"
}
}
}
I'm getting the same problem. I can create a subscription easily enough, and I can get the subscription details ONLY if I include the id in the call. But if I don't capture the id upon subscription creation, I've got an outstanding subscription that I can't delete. This will eventually cause throttling problems, but more importantly creates duplicate notifications because my app expects to delete all existing subscriptions before creating new ones during specific routines.
In other words:
This works: https://graph.microsoft.com/v1.0/subscriptions/[subscriptionId]
This does not work: https://graph.microsoft.com/v1.0/subscriptions
This failure makes it impossible to identify and delete outstanding subscriptions (when the subscription isn't captured during creation), thereby creating duplication and throttling issues.
Hello @AmirSohail-0150 - Looks like you are creating a new Subscription with the same details as you used for your previous Subscription.
Also, your previous Subscription hasn't deleted and you are trying to create another one with same details.
That is causing this issue.
Could you please verify once?
We are trying to repro this scenario at our end. If you have any business critical issue please Open a ticket by visiting the Azure Admin Center or visit the Microsoft 365 Admin Center and use the Support menu to Open a service request.
Also experiencing this exact issue. The API calls to https://graph.microsoft.com/v1.0/subscriptions are no longer returning anything (empty array.) Our application calls this API to look up existing subscriptions to know if new ones need to be created. The issue is resulting in duplicate subscription being added which causes problems for our users.
As far as I can tell this issue was introduced in the last ~36 hours with no code change to our application.
There looks to be a non-empty @OData.nextLink in the response given in the screenshot. Could you please make a call using the nextLink to retrieve more results?
Sometimes backend queries timeout and Database give the next link for continuing the query from the instance of the previous query result. Clients need to use the nextLink to navigate all pages
@AmirSohail-0150 - Could you please confirm if your issue has resolved with above suggestion or still looking for any help?
This does not solve the issue, because a lot of empty pages are returned. I have to make ~50 requests just to get 2-3 subscriptions and get to the end of the pagination. With this many requests, I will reach "429 - Too many Requests" pretty fast.
@ChetanSharmamsft-3456
This is not documented anywhere on the list subscriptions page. The document states "If successful, this method returns a 200 OK response code and a list of subscription objects in the response body".
An empty values array (especially on the first page) leads the user to conclude that there are no subscriptions. As a developer, if I create one subscription and my request for a list of subscriptions returns an empty set, then I must assume that the subscription list is broken. Pagination is not a solution for query timeouts - this should return a response code other than 200 (maybe 202) and a follow up link.
Furthermore, I echo @BenceGazder-4777's sentiment regarding throttling...requiring the client to repeatedly send requests is an undue burden and further reduces the client's ability to work within this environment.
To be clear, our development team has been forced to consider the possibility of migrating subscriptions for our products to other platforms because of this apparent failure.
List Subscription is currently not working out and giving out empty array as response.
For now as a work around you can do GET Subscription/ID to get the subscription. ( you will get the ID in response when you create the subscription you can store this ID and use it later when you want)
Along with empty array you will receive odata.NextLink , you need to traverse each page till the end of pagination to find all the active subscription.
Thanks for all the reports!
On Monday 2022/1/24, we were seeing lots of “Invalid Continuation Tokens” from CosmosDB resulting in 500’s returned to the client. This lasted for about 24 hours then dissipated. We’re not seeing any occurrence of this issue currently.
Zero results with a continuation token is not uncommon, historically our service returns these frequently. However, starting earlier this week (2022/1/24), we’ve had a sharp increase in the response, roughly 10x. As reported here, the tokens are valid and enumerating them will supply the full result sets but there are many more of them to process.
We are investigating the issue with the help of the CosmosDB support team.
I had to use this code to get all my subscriptions now. (sorry it won't let me post the actual code because it looks "suspicious"
Hello @AmirSohail-0150 - Looks like you are creating a new Subscription with the same details as you used for your previous Subscription.
Also, your previous Subscription hasn't deleted and you are trying to create another one with same details.
That is causing this
@02191796 No no if you check my postman request, first of all, I am checking that there is any subscription available with the exact details the API shows 0 results but when I am going to create a subscription it shows me that the subscription already exists.
a lot of empty pages are returned. I have to make ~50 requests just to get 2-3 subscriptions and get to the end of the pagination. With this many requests, I will reach "429 - Too many Requests"
It seems the same issue is happening again: https://github.com/microsoftgraph/microsoft-graph-docs/issues/15648
A lot of empty pages are returned and it causes a 429 error because of the request count.
When this problem is going to be resolved?
I've never seen this API call working:
https://docs.microsoft.com/en-us/graph/api/subscription-list?view=graph-rest-1.0&tabs=http
I've been developing my app for the past couple of months and have been seeing this issue intermittently throughout the whole time. My app creates subscriptions, stores subscriptionIds locally, then refreshes subscriptions using the subscriptionId five minutes before the expiration time. During development, I find that if I create a subscription from scratch then use the Graph API to list subscriptions, I first get the list of active subscriptions correctly. However, hours later, after the subscription has been continually refreshed and is still active (verified by continuing to get incoming change notification webhooks), the subscriptions list endpoint starts returning the empty array, and nothing seems to get this back into a working state for those existing subscriptions. My only course of action is to wait for those active subscriptions to expire and then start over again from scratch by creating new subscriptions.
27 people are following this question.
][1]
