dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review 

Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Josh van Leeuwen <me@joshvanl.dev>
This commit is contained in:
Josh van Leeuwen 2025-09-09 14:11:42 -04:00 committed by GitHub
parent be22cd0e5b
commit 3451cd3346
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md
View File

@ -227,8 +227,8 @@ This particular optimization only makes sense if you are saving large objects to
## Workflow Limitations
The more complex a workflow is (number of activities, child workflows, etc.), the more state operations it will perform per state store transaction.
All input & output values will also be saved to the workflow history, and will be part of an operation of these transactions.
The more complex a workflow is with number of activities, child workflows, etc, the more DB state operations it performs per state store transaction.
All input & output values are saved to the workflow history, and are part of an operation of these transactions.
CosmosDB has a [maximum document size of 2MB and maximum transaction size of 100 operations.](https://learn.microsoft.com/azure/cosmos-db/concepts-limits#per-request-limits).
This means that the workflow history must not exceed this size, meaning that CosmosDB is not suitable for workflows with large input/output values or larger complex workflows.