Setting offer throughput or autopilot on container is not supported for serverless accounts
See original GitHub issueVersion: 4.11.1
Describe the bug
Cosmos Serverless account cannot be configured. Throughput cannot be allocated to serverless account
To Reproduce
Steps to reproduce the behavior:
- Create Serverless Cosmos Account
- follow this guide
Exact error
System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 Substatus: 0 Reason: (Setting offer throughput or autopilot on container is not supported for serverless accounts.ActivityId: eeb8fa4c-323d-462e-96fe-9a079750a376, Microsoft.Azure.Documents.Common/2.11.0, Windows/10.0.19042 cosmos-netstandard-sdk/3.2.1).)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Setting offer throughput or autopilot on container is not ...
In general, setting an explicitly value for offer_throughput is not allowed for serverless type of accounts. So either you omit that value ...
Read more >Cosmos: Quick start --> Create Items Contaner --> HTTP ...
Clicking "Create 'Items' container" on Node.js tab = "Setting offer throughput or autopilot on container is not supported for serverless ...
Read more >Setting offer throughput or autopilot on container is not ...
Coding example for the question Setting offer throughput or autopilot on container is not supported for serverless accounts. Azure Cosmos DB migration tool....
Read more >Understanding Autopilot Mode in Azure Cosmos DB
Enter Autopilot mode Instead of manually setting throughput ourselves, we can set ... In your Cosmos DB account, click on New Container.
Read more >Understanding Autoscale Throughput in Azure Cosmos DB
Autoscale Throughput automatically scales the amount of throughput provisioned on your containers and databases based on the amount of traffic ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ankur198 You can create the CosmosDB account/db/container manually, beforehand and then use it. Make sure you use
/id
as partition key. As things stand currently, you cannot have it created automatically.@shwars This is not a bot framework issue. Please open a ticket within the Azure portal to have this addressed.