Get subscription API is not working.

Question

Get subscription API is not working.

Amir Sohail 401

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

ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T07:28:19.277+00:00

Hello @Amir Sohail - 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?
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T07:43:33.817+00:00

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.
CarlZhao-MSFT 20,376 Reputation points

2022-01-25T08:17:48.367+00:00

Has your original subscription been deleted?
Amir Sohail 401 Reputation points

2022-01-25T08:40:32.993+00:00

subscription is already created I need a subscription list and get subscription list is not working

response is empty : "value": []
Amir Sohail 401 Reputation points

2022-01-25T09:10:30.137+00:00

@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"
}
}
}
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T12:17:54.43+00:00

We will check on the logs and investigate it and update you accordingly.
Sam Nutkins 36 Reputation points

2022-01-25T19:14:14.47+00:00

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.
Billy Smith 31 Reputation points

2022-01-25T21:43:50.387+00:00
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.
Gustavo Vargas 26 Reputation points

2022-01-26T14:55:36.497+00:00

Same issue here

]1
Philip Rutberg 11 Reputation points

2022-01-26T15:17:43.143+00:00

I have the same issue, made a thread about it today as well as I couldn't find yours.

Subscriptions goes through successfully but doesn't exist when trying to get them through the /subscriptions endpoint.
Sam Nutkins 36 Reputation points

2022-01-26T18:57:33.63+00:00
Wanted to share this info after researching the issue a bit further.

When initially calling the mentioned API method, the results are as follows, despite there being known subscriptions present

{ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#subscriptions", "@odata.nextLink": "https://graph.microsoft.com/v1.0/subscriptions?$skiptoken=OMITTED", "value":[] }

Notice the @odata.nextLink property - I have found that following these links repeatedly as they are provided in response does eventually get you to your subscriptions. Note that for me to see them I had to go through 5-10 nextLinks, and at times continuing to skip through empty pages, but I do eventually find the subscriptions.

This seems more like a workaround and I definitely still believe this to be a bug in Graph, as the nextLink should not be necessary unless there is a full page of results already returned. Hope this helps others.
Bence Gazder 31 Reputation points

2022-01-27T11:31:50.913+00:00

Same for me. The next link itself is valid, but it will return an empty value array a lot of times.
Sayali-MSFT 1,611 Reputation points Microsoft Vendor

2022-02-02T14:06:07.377+00:00

We are Unable to repro the issue, We tried with Application as well as Delegated permission, It's working fine for us. Could you first create the Subscription then call the Graph API for Getting the List of Subscription?
Graph API:- GET https://graph.microsoft.com/v1.0/subscriptions
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-02-04T13:24:42.533+00:00

Hello @Sam Nutkins , @Amir Sohail , @Billy Smith , @Gustavo Vargas , @Bence Gazder ,
Could you please share the request and response details with it's request id, so that we can check it from our end.

Thanks!!
Bence Gazder 1 Reputation point

2022-02-04T14:33:33.557+00:00

The issue is already solved on our end, I cannot reproduce it.
Oleksii Burchynskyi 1 Reputation point

2022-07-19T21:05:09.347+00:00

When this problem is going to be resolved?
I've never seen this API call working:
https://learn.microsoft.com/en-us/graph/api/subscription-list?view=graph-rest-1.0&tabs=http
Sayali-MSFT 1,611 Reputation points Microsoft Vendor

2022-07-20T06:56:28.48+00:00

Hello @Oleksii Burchynskyi , We are Unable to repro the issue, We tried with Application as well as Delegated permission, It's working fine for us. Could you first create the Subscription then call the Graph API for Getting the List of Subscription?

Graph API:-

GET https://graph.microsoft.com/v1.0/subscriptions

Thanks!!

ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T07:28:19.277+00:00

Hello @Amir Sohail - 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?
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T07:43:33.817+00:00

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.
CarlZhao-MSFT 20,376 Reputation points

2022-01-25T08:17:48.367+00:00

Has your original subscription been deleted?
Amir Sohail 401 Reputation points

2022-01-25T08:40:32.993+00:00

subscription is already created I need a subscription list and get subscription list is not working

response is empty : "value": []
Amir Sohail 401 Reputation points

2022-01-25T09:10:30.137+00:00

@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"
}
}
}
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-25T12:17:54.43+00:00

We will check on the logs and investigate it and update you accordingly.
Sam Nutkins 36 Reputation points

2022-01-25T19:14:14.47+00:00

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.
Billy Smith 31 Reputation points

2022-01-25T21:43:50.387+00:00

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.
Gustavo Vargas 26 Reputation points

2022-01-26T14:55:36.497+00:00

Same issue here

]1
Philip Rutberg 11 Reputation points

2022-01-26T15:17:43.143+00:00

I have the same issue, made a thread about it today as well as I couldn't find yours.

Subscriptions goes through successfully but doesn't exist when trying to get them through the /subscriptions endpoint.
Sam Nutkins 36 Reputation points

2022-01-26T18:57:33.63+00:00

Wanted to share this info after researching the issue a bit further.

When initially calling the mentioned API method, the results are as follows, despite there being known subscriptions present

{ "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#subscriptions", "@odata.nextLink": "https://graph.microsoft.com/v1.0/subscriptions?$skiptoken=OMITTED", "value":[] }

Notice the @odata.nextLink property - I have found that following these links repeatedly as they are provided in response does eventually get you to your subscriptions. Note that for me to see them I had to go through 5-10 nextLinks, and at times continuing to skip through empty pages, but I do eventually find the subscriptions.

This seems more like a workaround and I definitely still believe this to be a bug in Graph, as the nextLink should not be necessary unless there is a full page of results already returned. Hope this helps others.
Bence Gazder 31 Reputation points

2022-01-27T11:31:50.913+00:00

Same for me. The next link itself is valid, but it will return an empty value array a lot of times.
Sayali-MSFT 1,611 Reputation points Microsoft Vendor

2022-02-02T14:06:07.377+00:00

We are Unable to repro the issue, We tried with Application as well as Delegated permission, It's working fine for us. Could you first create the Subscription then call the Graph API for Getting the List of Subscription?
Graph API:- GET https://graph.microsoft.com/v1.0/subscriptions
ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-02-04T13:24:42.533+00:00

Hello @Sam Nutkins , @Amir Sohail , @Billy Smith , @Gustavo Vargas , @Bence Gazder ,
Could you please share the request and response details with it's request id, so that we can check it from our end.

Thanks!!
Bence Gazder 1 Reputation point

2022-02-04T14:33:33.557+00:00

The issue is already solved on our end, I cannot reproduce it.
Oleksii Burchynskyi 1 Reputation point

2022-07-19T21:05:09.347+00:00

When this problem is going to be resolved?
I've never seen this API call working:
https://learn.microsoft.com/en-us/graph/api/subscription-list?view=graph-rest-1.0&tabs=http
Sayali-MSFT 1,611 Reputation points Microsoft Vendor

2022-07-20T06:56:28.48+00:00

Hello @Oleksii Burchynskyi , We are Unable to repro the issue, We tried with Application as well as Delegated permission, It's working fine for us. Could you first create the Subscription then call the Graph API for Getting the List of Subscription?

Graph API:-

GET https://graph.microsoft.com/v1.0/subscriptions

Thanks!!

Answer 1

Dan Espich 36

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"

Reem Karm Mahmoud 56 Reputation points

2022-06-06T18:55:23.197+00:00

thanks
Konstantin Gapeev 1 Reputation point

2022-06-20T18:34:40.61+00:00

Thank you very much!

Answer 2

venkat 116

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

ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-01-27T09:41:38.86+00:00

@Amir Sohail - Could you please confirm if your issue has resolved with above suggestion or still looking for any help?
Bence Gazder 31 Reputation points

2022-01-27T11:29:21.777+00:00

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.
Billy Smith 31 Reputation points

2022-01-27T17:29:53.007+00:00

@ChetanSharmamsft
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 @Bence Gazder '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.

Answer 3

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.

Answer 4

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.

ChetanSharmamsft 781 Reputation points Microsoft Vendor

2022-03-06T13:46:43.867+00:00

@venkat - Is there any update on the investigation part ?

Answer 5

نوره على على أبو العلا 26

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"

نوره على على أبو العلا 26 Reputation points

2022-06-15T17:07:45.87+00:00

Thankyou

Get subscription API is not working.

9 answers

Activity