From 449711f9ffacb9089fc110672703e25bcffbf8cf Mon Sep 17 00:00:00 2001 From: joshvanl Date: Mon, 8 Sep 2025 13:27:25 -0400 Subject: [PATCH 01/11] [1.16] Adds workflow limitations Updates state store table to include supported stores. Adds a warning emoji to state stores which have workflow limitations. Adds workflow limitation sections to the cosmosDB & dynamodb setup docs. Signed-off-by: joshvanl --- .../supported-state-stores/setup-azure-cosmosdb.md | 8 ++++++++ .../supported-state-stores/setup-dynamodb.md | 6 ++++++ daprdocs/data/components/state_stores/aws.yaml | 2 +- daprdocs/data/components/state_stores/azure.yaml | 4 ++-- daprdocs/data/components/state_stores/generic.yaml | 6 +++--- daprdocs/data/components/state_stores/oracle.yaml | 2 +- daprdocs/layouts/_partials/components/state-stores.html | 4 ++++ 7 files changed, 25 insertions(+), 7 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 2e67d46c137..03f2c65769c 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -225,6 +225,14 @@ This particular optimization only makes sense if you are saving large objects to {{% /alert %}} +## 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. +CosmosDB has a [maximum document size of 2MB and maximum transaction size of 100 operations.](https://learn.microsoft.com/en-us/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. + + ## Related links - [Basic schema for a Dapr component]({{% ref component-schema %}}) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md index 5a45e374d90..5888a004e18 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md @@ -158,6 +158,12 @@ $ aws dynamodb get-item \ } ``` +## 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. +The maximum number of operations that can be performed by DynamoDB in a [single transaction is 100](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html). +This means that DynamoDB can only hadle workflows with a limited complexity, meaning it is not suitable for all workflow scenarios. + ## Related links - [Basic schema for a Dapr component]({{% ref component-schema %}}) diff --git a/daprdocs/data/components/state_stores/aws.yaml b/daprdocs/data/components/state_stores/aws.yaml index f6d8d1b1a77..fd2aef8e6d6 100644 --- a/daprdocs/data/components/state_stores/aws.yaml +++ b/daprdocs/data/components/state_stores/aws.yaml @@ -8,4 +8,4 @@ transactions: true etag: true ttl: true - workflow: false + workflow_warning: workflow-limitations diff --git a/daprdocs/data/components/state_stores/azure.yaml b/daprdocs/data/components/state_stores/azure.yaml index 287477de780..30b0ddd549f 100644 --- a/daprdocs/data/components/state_stores/azure.yaml +++ b/daprdocs/data/components/state_stores/azure.yaml @@ -19,7 +19,7 @@ transactions: true etag: true ttl: true - workflow: false + workflow_warning: workflow-limitations - component: Microsoft SQL Server link: setup-sqlserver state: Stable @@ -30,7 +30,7 @@ transactions: true etag: true ttl: true - workflow: false + workflow: true - component: Azure Table Storage link: setup-azure-tablestorage state: Stable diff --git a/daprdocs/data/components/state_stores/generic.yaml b/daprdocs/data/components/state_stores/generic.yaml index 289d8ce4305..8d8ce44184c 100644 --- a/daprdocs/data/components/state_stores/generic.yaml +++ b/daprdocs/data/components/state_stores/generic.yaml @@ -52,7 +52,7 @@ transactions: true etag: true ttl: true - workflow: false + workflow: true - component: Hashicorp Consul link: setup-consul state: Alpha @@ -140,7 +140,7 @@ transactions: true etag: true ttl: true - workflow: false + workflow: true - component: PostgreSQL v1 link: setup-postgresql-v1 state: Stable @@ -195,7 +195,7 @@ transactions: true etag: true ttl: true - workflow: false + workflow: true - component: Zookeeper link: setup-zookeeper state: Alpha diff --git a/daprdocs/data/components/state_stores/oracle.yaml b/daprdocs/data/components/state_stores/oracle.yaml index eae48304fde..fc5136684b6 100644 --- a/daprdocs/data/components/state_stores/oracle.yaml +++ b/daprdocs/data/components/state_stores/oracle.yaml @@ -9,7 +9,7 @@ etag: true ttl: true query: false - workflow: false + workflow: true - component: Coherence link: setup-coherence state: Alpha diff --git a/daprdocs/layouts/_partials/components/state-stores.html b/daprdocs/layouts/_partials/components/state-stores.html index e486f05bbc1..fd6e463a7f6 100644 --- a/daprdocs/layouts/_partials/components/state-stores.html +++ b/daprdocs/layouts/_partials/components/state-stores.html @@ -67,6 +67,10 @@

{{ $group }}

{{ if .features.workflow }} ✅ + {{ else if .features.workflow_warning }} + + ⚠️ + {{else}} Workflow: Not supported {{ end }} From be22cd0e5bcc554acb64b8dffc83982b83f87887 Mon Sep 17 00:00:00 2001 From: joshvanl Date: Mon, 8 Sep 2025 16:55:52 -0400 Subject: [PATCH 02/11] Updates limitation sections. Remove localizations Signed-off-by: joshvanl --- .../building-blocks/workflow/workflow-overview.md | 4 +++- .../supported-state-stores/setup-azure-cosmosdb.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-overview.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-overview.md index 67e4941f880..b1b9cd752f7 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-overview.md @@ -110,7 +110,9 @@ Want to skip the quickstarts? Not a problem. You can try out the workflow buildi ## Limitations -- **State stores:** Due to underlying limitations in some database choices, more commonly NoSQL databases, you might run into limitations around storing internal states. For example, CosmosDB has a maximum single operation item limit of only 100 states in a single request. +- **State stores:** You can only use state stores which support workflows, as [described here]({{% ref supported-state-stores %}}). +- Azure Cosmos DB has [payload and workflow complexity limitations]({{% ref "setup-azure-cosmosdb.md#workflow-limitations" %}}). +- AWS DynamoDB has [workflow complexity limitations]({{% ref "setup-azure-cosmosdb.md#workflow-limitations" %}}). ## Watch the demo diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 03f2c65769c..6bd9746e3d5 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -229,7 +229,7 @@ This particular optimization only makes sense if you are saving large objects to 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. -CosmosDB has a [maximum document size of 2MB and maximum transaction size of 100 operations.](https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits#per-request-limits). +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. From 3451cd334663afebb273a500e796ed76ca8808fa Mon Sep 17 00:00:00 2001 From: Josh van Leeuwen Date: Tue, 9 Sep 2025 14:11:42 -0400 Subject: [PATCH 03/11] Apply suggestions from code review Co-authored-by: Mark Fussell Signed-off-by: Josh van Leeuwen --- .../supported-state-stores/setup-azure-cosmosdb.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 6bd9746e3d5..9bbc16a04d1 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -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. From 2c9382c905d02a6a874684c58f8906c3dc680c75 Mon Sep 17 00:00:00 2001 From: joshvanl Date: Tue, 9 Sep 2025 14:30:02 -0400 Subject: [PATCH 04/11] Adds section on the number of records that are saved by workflow shape Signed-off-by: joshvanl --- .../workflow/workflow-architecture.md | 14 ++++++++++++++ .../supported-state-stores/setup-azure-cosmosdb.md | 3 ++- .../supported-state-stores/setup-dynamodb.md | 1 + 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md index 2fdd37d1cf8..ba956294526 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md @@ -175,6 +175,20 @@ Similarly, if a state store imposes restrictions on the size of a batch transact Workflow state can be purged from a state store, including all its history. Each Dapr SDK exposes APIs for purging all metadata related to specific workflow instances. +#### State store record count + +The number of records which will be saved as history in the state store per workflow run is determined by its complexity or "shape", i.e. the number of activities, timers, sub-workflows etc. +The following table shows a general guide to the number of records that are saved by different workflow tasks. +This number may be larger or smaller depending on retries or concurrency. + +| Task type | Number of records saved | +| ----------|-------------------------| +| Start workflow | 5 records | +| Call activity | 3 records | +| Timer | 3 records | +| Raise event | 3 records | +| Start child workflow | 8 records | + ## Workflow scalability Because Dapr Workflows are internally implemented using actors, Dapr Workflows have the same scalability characteristics as actors. diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 9bbc16a04d1..69142102654 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -230,8 +230,9 @@ This particular optimization only makes sense if you are saving large objects to 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). +Attempting to write to CosmosDB beyond these limits will result in an error code of `413`. 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. - +A general guide to the number of records that are saved during a workflow executon can be found [here]({{% ref "workflow-architecture.md#state-store-record-count" %}}). ## Related links diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md index 5888a004e18..00651b2a808 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md @@ -163,6 +163,7 @@ $ aws dynamodb get-item \ The more complex a workflow is (number of activities, child workflows, etc.), the more state operations it will perform per state store transaction. The maximum number of operations that can be performed by DynamoDB in a [single transaction is 100](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html). This means that DynamoDB can only hadle workflows with a limited complexity, meaning it is not suitable for all workflow scenarios. +A general guide to the number of records that are saved during a workflow executon can be found [here]({{% ref "workflow-architecture.md#state-store-record-count" %}}). ## Related links From 5b7665c16b82a7033076e34413487b9dcd82527e Mon Sep 17 00:00:00 2001 From: joshvanl Date: Tue, 9 Sep 2025 15:39:10 -0400 Subject: [PATCH 05/11] Mark dynamo and cosmosdb state stores as not supporting workflows in table Signed-off-by: joshvanl --- daprdocs/data/components/state_stores/aws.yaml | 2 +- daprdocs/data/components/state_stores/azure.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/data/components/state_stores/aws.yaml b/daprdocs/data/components/state_stores/aws.yaml index fd2aef8e6d6..f6d8d1b1a77 100644 --- a/daprdocs/data/components/state_stores/aws.yaml +++ b/daprdocs/data/components/state_stores/aws.yaml @@ -8,4 +8,4 @@ transactions: true etag: true ttl: true - workflow_warning: workflow-limitations + workflow: false diff --git a/daprdocs/data/components/state_stores/azure.yaml b/daprdocs/data/components/state_stores/azure.yaml index 30b0ddd549f..b340a26db71 100644 --- a/daprdocs/data/components/state_stores/azure.yaml +++ b/daprdocs/data/components/state_stores/azure.yaml @@ -19,7 +19,7 @@ transactions: true etag: true ttl: true - workflow_warning: workflow-limitations + workflow: false - component: Microsoft SQL Server link: setup-sqlserver state: Stable From dee2fa63f6290c99e4d3ba5f7124b5a01a5ee78d Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Tue, 9 Sep 2025 20:33:37 -0700 Subject: [PATCH 06/11] Update daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md Signed-off-by: Mark Fussell --- .../supported-state-stores/setup-azure-cosmosdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 69142102654..4b7da0a3812 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -230,7 +230,7 @@ This particular optimization only makes sense if you are saving large objects to 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). -Attempting to write to CosmosDB beyond these limits will result in an error code of `413`. +Attempting to write to CosmosDB beyond these limits results in an error code of `413`. 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. A general guide to the number of records that are saved during a workflow executon can be found [here]({{% ref "workflow-architecture.md#state-store-record-count" %}}). From cc8281f7effea9b5a0f206603115a53c96186fc3 Mon Sep 17 00:00:00 2001 From: Josh van Leeuwen Date: Wed, 10 Sep 2025 09:19:04 -0400 Subject: [PATCH 07/11] Apply suggestions from code review Co-authored-by: Mark Fussell Signed-off-by: Josh van Leeuwen --- .../building-blocks/workflow/workflow-architecture.md | 2 +- .../supported-state-stores/setup-dynamodb.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md index ba956294526..e5d77c2c18e 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md @@ -177,7 +177,7 @@ Each Dapr SDK exposes APIs for purging all metadata related to specific workflow #### State store record count -The number of records which will be saved as history in the state store per workflow run is determined by its complexity or "shape", i.e. the number of activities, timers, sub-workflows etc. +The number of records which are saved as history in the state store per workflow run is determined by its complexity or "shape". In other words, the number of activities, timers, sub-workflows etc. The following table shows a general guide to the number of records that are saved by different workflow tasks. This number may be larger or smaller depending on retries or concurrency. diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md index 00651b2a808..a6388bfea98 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md @@ -160,9 +160,9 @@ $ aws dynamodb get-item \ ## 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. +The more complex a workflow is (number of activities, child workflows, etc.), the more state operations it performs per state store transaction. The maximum number of operations that can be performed by DynamoDB in a [single transaction is 100](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html). -This means that DynamoDB can only hadle workflows with a limited complexity, meaning it is not suitable for all workflow scenarios. +This means that DynamoDB can only handle workflows with a limited complexity, meaning it is not suitable for all workflow scenarios. A general guide to the number of records that are saved during a workflow executon can be found [here]({{% ref "workflow-architecture.md#state-store-record-count" %}}). ## Related links From 792650a630af41eb4fb8e3167857720660079546 Mon Sep 17 00:00:00 2001 From: joshvanl Date: Wed, 10 Sep 2025 09:50:42 -0400 Subject: [PATCH 08/11] Adds production warning to cosmos & dynamo Signed-off-by: joshvanl --- .../supported-state-stores/setup-azure-cosmosdb.md | 7 +++++++ .../supported-state-stores/setup-dynamodb.md | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 4b7da0a3812..4306667a087 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -227,6 +227,13 @@ This particular optimization only makes sense if you are saving large objects to ## Workflow Limitations +{{% alert title="Note" color="primary" %}} + +As described below, CosmosDB has limitations that likely make it unsuitable for production environments. +There is currently no path for migrating Workflow data from CosmosDB to another state store, meaning exceeding these limits in production will result in failed workflows this no workaround. + +{{% /alert %}} + 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). diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md index a6388bfea98..e0ca89c5833 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md @@ -160,6 +160,13 @@ $ aws dynamodb get-item \ ## Workflow Limitations +{{% alert title="Note" color="primary" %}} + +As described below, DynamoDB has limitations that likely make it unsuitable for production environments. +There is currently no path for migrating Workflow data from DynamoDB to another state store, meaning exceeding these limits in production will result in failed workflows this no workaround. + +{{% /alert %}} + The more complex a workflow is (number of activities, child workflows, etc.), the more state operations it performs per state store transaction. The maximum number of operations that can be performed by DynamoDB in a [single transaction is 100](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html). This means that DynamoDB can only handle workflows with a limited complexity, meaning it is not suitable for all workflow scenarios. From ec74420078cf771df3d30332304bbe403d093afd Mon Sep 17 00:00:00 2001 From: joshvanl Date: Wed, 10 Sep 2025 14:13:22 -0400 Subject: [PATCH 09/11] Removes warning from state template Signed-off-by: joshvanl --- daprdocs/layouts/_partials/components/state-stores.html | 4 ---- 1 file changed, 4 deletions(-) diff --git a/daprdocs/layouts/_partials/components/state-stores.html b/daprdocs/layouts/_partials/components/state-stores.html index fd6e463a7f6..e486f05bbc1 100644 --- a/daprdocs/layouts/_partials/components/state-stores.html +++ b/daprdocs/layouts/_partials/components/state-stores.html @@ -67,10 +67,6 @@

{{ $group }}

{{ if .features.workflow }} ✅ - {{ else if .features.workflow_warning }} - - ⚠️ - {{else}} Workflow: Not supported {{ end }} From 771c57b26ed407566c0fcf2b469d81236b32200d Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Wed, 10 Sep 2025 15:46:16 -0700 Subject: [PATCH 10/11] Update daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md Signed-off-by: Mark Fussell --- .../supported-state-stores/setup-azure-cosmosdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md index 4306667a087..dc225eee5d5 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md @@ -230,7 +230,7 @@ This particular optimization only makes sense if you are saving large objects to {{% alert title="Note" color="primary" %}} As described below, CosmosDB has limitations that likely make it unsuitable for production environments. -There is currently no path for migrating Workflow data from CosmosDB to another state store, meaning exceeding these limits in production will result in failed workflows this no workaround. +There is currently no path for migrating Workflow data from CosmosDB to another state store, meaning exceeding these limits in production will result in failed workflows with no workaround. {{% /alert %}} From ed07373152c02e05994b2ec2a0948b438ac8a83c Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Wed, 10 Sep 2025 15:46:25 -0700 Subject: [PATCH 11/11] Update daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md Signed-off-by: Mark Fussell --- .../supported-state-stores/setup-dynamodb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md index e0ca89c5833..082d4e4875a 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md @@ -163,7 +163,7 @@ $ aws dynamodb get-item \ {{% alert title="Note" color="primary" %}} As described below, DynamoDB has limitations that likely make it unsuitable for production environments. -There is currently no path for migrating Workflow data from DynamoDB to another state store, meaning exceeding these limits in production will result in failed workflows this no workaround. +There is currently no path for migrating Workflow data from DynamoDB to another state store, meaning exceeding these limits in production will result in failed workflows with no workaround. {{% /alert %}}