Unable to Create Stored Procedure in Azure Cosmos DB Container

Question

Unable to Create Stored Procedure in Azure Cosmos DB Container

Kirankumar Bharsadiya 60

Experiencing an issue when attempting to create a new stored procedure in a specific container within Azure Cosmos DB. The error encountered is as follows:

Error while creating stored procedure spSelectCount: Message: {"code":"NotFound","message":"Entity with the specified id does not exist in the system. More info: https://aka.ms/cosmosdb-tsg-not-found\r\nActivityId: d5d84b7c-aba3-45da-95fd-349e866afb65, Microsoft.Azure.Documents.Common/2.14.0"}, Request URI: /dbs/myDatabaseName/colls/myContainerName/sprocs/spSelectCount, RequestStats: , SDK: Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Documents.Common/2.14.0 ActivityId: ea9f2fee-8b77-4bfd-9b9f-28afb2866665, Microsoft.Azure.Documents.Common/2.14.0

The following verifications have been made:

The stored procedure does not exist in the container where the creation is attempted.
The stored procedure exists in a different container with the same ID.

It is unexpected to receive a "Not Found" error upon creation, as a conflict should ideally occur if the stored procedure already existed. Assistance is needed to resolve this conflicting scenario.

Azar 29,520 Reputation points MVP Volunteer Moderator

2025-04-23T16:37:08.79+00:00

Hi there Kirankumar Bharsadiya

Thanks for using QandA platform

This typically indicates that the specified container or database doesn't exist or isn't accessible at the time of the request not that the stored procedure itself is missing. Even if the stored procedure doesn't already exist (which should normally result in a conflict error if it did), Cosmos DB will return a "NotFound" error if the parent container path is incorrect or not found.

verify that your SDK client is correctly configured with the right endpoint and keys. This issue can also happen if the container creation hasn’t completed yet in scripts or CI/CD flows. You can refer to the official docs on stored procedures and the troubleshooting guide for NotFound errors

If this helps kindly accept the answer thanks much.
Kirankumar Bharsadiya 60 Reputation points

2025-04-23T17:17:53.2033333+00:00

I am facing this issue while creating directly in azure cosmos db account in azure portal itself.
Adithya Prasad K 1,375 Reputation points Microsoft External Staff Moderator

2025-04-24T17:38:44.82+00:00
Hello Kirankumar Bharsadiya ,

I understand your frustration with this unexpected behavior when trying to create the stored procedure. Here are a few thoughts on what might be happening and some recommendations for next steps:

Scoped Uniqueness of Stored Procedures: In Azure Cosmos DB, stored procedures are scoped to the collection (container), so having the same stored procedure ID in different containers is normally permitted. However, the error you’re encountering indicates that the system is trying to access an entity by that ID and isn’t finding it in the expected context. This suggests that there might be an internal conflict or misrouting when the portal attempts the creation.

Possible Causes:

Resource Link or Metadata Mismatch: The portal might be incorrectly resolving the resource link for your target container. If a stored procedure with the same ID exists in another container, the system could be confused about which one to reference—even though they are logically separate.

Cache or Session Issues: There is also a possibility that cached metadata or a lingering session is causing the portal to check for the stored procedure in the wrong container.

Portal Bug: Since you are creating the stored procedure directly in the Azure Portal, this behavior might be an anomaly or bug in the portal experience. Running the same operation via one of the Cosmos DB SDKs or REST API could help isolate whether the issue is portal-specific.

Recommendations:

Verify Container Selection: Double-check that the creation process is targeting the intended container. Ensure that the container’s resource link or ID is correct in the creation flow.

Try a Different Approach: If possible, attempt to create the stored procedure using the Cosmos DB SDK (for example, via .NET or Node.js) or through the REST API. This may bypass any portal-specific issues and give a clearer error message if something else is at play.

Rename or Isolate: As a test, try creating the stored procedure under a different ID in the target container to see if the conflict is solely due to the duplicate name across containers.

Consult Official Troubleshooting Guidance: The Troubleshoot Azure Cosmos DB Not Found Exceptions guide may offer additional insights into why a NotFound error might be returned during the creation process, especially if the system is expecting an entity that isn’t present.

I hope these suggestions help clarify the scenario and guide you toward a resolution. Please let me know if you have further questions or need additional assistance.
Kirankumar Bharsadiya 60 Reputation points

2025-04-25T11:53:28.32+00:00

I have tried with SDK but, while doing using SDK getting the issue mentioned in following question. This will provide more context. First ever, I tried using the SDK and then went to direct portal to check.
https://learn.microsoft.com/en-us/answers/questions/2260573/conflicting-behavior-when-creating-stored-procedur
Narendra Pakkirigari 475 Reputation points Microsoft External Staff Moderator

2025-04-29T08:20:08.74+00:00

Hi Kirankumar Bharsadiya,

In the Azure portal, you must explicitly select the correct container not just the database before adding a stored procedure. Cosmos DB stores procedures at the container collection level, not at the database level. Expand your database node and also the container node and verify the stored procedure is present in that particular container or not.
Narendra Pakkirigari 475 Reputation points Microsoft External Staff Moderator

2025-04-30T05:31:18.77+00:00

Hi Kirankumar Bharsadiya,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Azar 29,520 Reputation points MVP Volunteer Moderator

2025-04-23T16:37:08.79+00:00

Hi there Kirankumar Bharsadiya

Thanks for using QandA platform

This typically indicates that the specified container or database doesn't exist or isn't accessible at the time of the request not that the stored procedure itself is missing. Even if the stored procedure doesn't already exist (which should normally result in a conflict error if it did), Cosmos DB will return a "NotFound" error if the parent container path is incorrect or not found.

verify that your SDK client is correctly configured with the right endpoint and keys. This issue can also happen if the container creation hasn’t completed yet in scripts or CI/CD flows. You can refer to the official docs on stored procedures and the troubleshooting guide for NotFound errors

If this helps kindly accept the answer thanks much.
Kirankumar Bharsadiya 60 Reputation points

2025-04-23T17:17:53.2033333+00:00

I am facing this issue while creating directly in azure cosmos db account in azure portal itself.
Kirankumar Bharsadiya 60 Reputation points

2025-04-25T11:53:28.32+00:00

I have tried with SDK but, while doing using SDK getting the issue mentioned in following question. This will provide more context. First ever, I tried using the SDK and then went to direct portal to check.
https://learn.microsoft.com/en-us/answers/questions/2260573/conflicting-behavior-when-creating-stored-procedur
Narendra Pakkirigari 475 Reputation points Microsoft External Staff Moderator

2025-04-29T08:20:08.74+00:00

Hi Kirankumar Bharsadiya,

In the Azure portal, you must explicitly select the correct container not just the database before adding a stored procedure. Cosmos DB stores procedures at the container collection level, not at the database level. Expand your database node and also the container node and verify the stored procedure is present in that particular container or not.
Narendra Pakkirigari 475 Reputation points Microsoft External Staff Moderator

2025-04-30T05:31:18.77+00:00

Hi Kirankumar Bharsadiya,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Follow the below steps to create Stored Procedure in Azure Cosmos DB Container:

Step 1:

After creating a Azure Cosmos DB account, create a database and a container. Below is my database db1 and a container cont1.

Step 2:

You can create Stored Procedure manually, under database db1 you can find a container cont1, under container you can find items, click on ... and select New Stored Procedure or you can find a direct option New Stored Procedure to create it as shown in the below image.

image (1)

Database ---> Container ---> Items ---> New Stored Procedure

New Stored Procedure created successfully, as shown in the below image.

image (2)

Share via

Unable to Create Stored Procedure in Azure Cosmos DB Container

1 answer

Your answer