Update functions-host-json-durabletask.md

Making some updates to the host.json reference for Durable Functions to account for some recent confusion in a customer issue.

Author: cgillum

includes/functions-host-json-durabletask.md

@@ -4,7 +4,7 @@ description: include file
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 03/14/2019
+ms.date: 04/17/2025
 ms.author: glenga
 ms.custom: include file
 ---
@@ -32,8 +32,8 @@ Configuration settings for [Durable Functions](../articles/azure-functions/durab
       "partitionCount": 4,
       "trackingStoreConnectionStringName": "TrackingStorage",
       "trackingStoreNamePrefix": "DurableTask",
-      "useLegacyPartitionManagement": true,
-      "useTablePartitionManagement": false,
+      "useLegacyPartitionManagement": false,
+      "useTablePartitionManagement": true,
       "workItemQueueVisibilityTimeout": "00:05:00",
     },
     "tracing": {
@@ -56,11 +56,13 @@ Configuration settings for [Durable Functions](../articles/azure-functions/durab
     },
     "maxConcurrentActivityFunctions": 10,
     "maxConcurrentOrchestratorFunctions": 10,
+    "maxConcurrentEntityFunctions": 10,
     "extendedSessionsEnabled": false,
     "extendedSessionIdleTimeoutInSeconds": 30,
     "useAppLease": true,
     "useGracefulShutdown": false,
     "maxEntityOperationBatchSize": 50,
+    "maxOrchestrationActions": 100000,
     "storeInputsInOrchestrationHistory": false
   }
  }
@@ -103,12 +105,13 @@ Task hub names must start with a letter and consist of only letters and numbers.
 |---------|---------|----------|
 |hubName|TestHubName (DurableFunctionsHub if using Durable Functions 1.x)|Alternate [task hub](../articles/azure-functions/durable/durable-functions-task-hubs.md) names can be used to isolate multiple Durable Functions applications from each other, even if they're using the same storage backend.|
 |controlQueueBatchSize|32|The number of messages to pull from the control queue at a time.|
-|controlQueueBufferThreshold| **Consumption plan for Python**: 32 <br> **Consumption plan for JavaScript and C#**: 128 <br> **Dedicated/Premium plan**: 256 |The number of control queue messages that can be buffered in memory at a time, at which point the dispatcher will wait before dequeuing any additional messages.|
-|partitionCount |4|The partition count for the control queue. May be a positive integer between 1 and 16.|
+|controlQueueBufferThreshold| **Consumption plan for Python**: 32 <br> **Consumption plan for other languages**: 128 <br> **Dedicated/Premium plan**: 256 |The number of control queue messages that can be buffered in memory at a time, at which point the dispatcher will wait before dequeuing any additional messages. In some situations, reducing this value can significantly reduce memory consumption.|
+|partitionCount |4|The partition count for the control queue. May be a positive integer between 1 and 16. Changing this value requires configuring a new task hub.|
 |controlQueueVisibilityTimeout |5 minutes|The visibility timeout of dequeued control queue messages.|
 |workItemQueueVisibilityTimeout |5 minutes|The visibility timeout of dequeued work item  queue messages.|
 |maxConcurrentActivityFunctions | **Consumption plan**: 10 <br> **Dedicated/Premium plan**: 10X the number of processors on the current machine|The maximum number of activity functions that can be processed concurrently on a single host instance.|
 |maxConcurrentOrchestratorFunctions | **Consumption plan**: 5 <br> **Dedicated/Premium plan**: 10X the number of processors on the current machine |The maximum number of orchestrator functions that can be processed concurrently on a single host instance.|
+|maxConcurrentEntityFunctions | **Consumption plan**: 5 <br> **Dedicated/Premium plan**: 10X the number of processors on the current machine |The maximum number of entity functions that can be processed concurrently on a single host instance. This setting is only applicable when using the [durable task scheduler](../articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md). Otherwise, the maximum number of concurrent entity executions is limited to `maxConcurrentOrchestratorFunctions`.|
 |maxQueuePollingInterval|30 seconds|The maximum control and work-item queue polling interval in the *hh:mm:ss* format. Higher values can result in higher message processing latencies. Lower values can result in higher storage costs because of increased storage transactions.|
 |connectionName (2.7.0 and later)<br/>connectionStringName (2.x)<br/>azureStorageConnectionStringName (1.x) |AzureWebJobsStorage|The name of an app setting or setting collection that specifies how to connect to the underlying Azure Storage resources. When a single app setting is provided, it should be an Azure Storage connection string.|
 |trackingStoreConnectionName (2.7.0 and later)<br/>trackingStoreConnectionStringName||The name of an app setting or setting collection that specifies how to connect to the History and Instances tables. When a single app setting is provided, it should be an Azure Storage connection string. If not specified, the `connectionStringName` (Durable 2.x) or `azureStorageConnectionStringName` (Durable 1.x) connection is used.|
@@ -121,8 +124,8 @@ Task hub names must start with a letter and consist of only letters and numbers.
 |eventGridPublishRetryInterval|5 minutes|The Event Grid publishes retry interval in the *hh:mm:ss* format.|
 |eventGridPublishEventTypes||A list of event types to publish to Event Grid. If not specified, all event types will be published. Allowed values include `Started`, `Completed`, `Failed`, `Terminated`.|
 |useAppLease|true|When set to `true`, apps will require acquiring an app-level blob lease before processing task hub messages. For more information, see the [disaster recovery and geo-distribution](../articles/azure-functions/durable/durable-functions-disaster-recovery-geo-distribution.md) documentation. Available starting in v2.3.0.
-|useLegacyPartitionManagement|false|When set to `false`, uses a partition management algorithm that reduces the possibility of duplicate function execution when scaling out. Available starting in v2.3.0.|
-|useTablePartitionManagement|false|When set to `true`, uses a partition management algorithm designed to reduce costs for Azure Storage V2 accounts. Available starting in WebJobs.Extensions.DurableTask v2.10.0. When enabled in WebJobs.Extensions.DurableTask v2.x or Worker.Extensions.DurableTask versions earlier than v1.2.x, Managed Identity isn't supported.|
+|useLegacyPartitionManagement|false|When set to `false`, uses a partition management algorithm that reduces the possibility of duplicate function execution when scaling out. Available starting in v2.3.0. **Setting this value to `true` is not recommended**.|
+|useTablePartitionManagement|`true` in v3.x extension versions<br>`false` in v2.x extension versions|When set to `true`, uses a partition management algorithm designed to reduce costs for Azure Storage V2 accounts. Available starting in WebJobs.Extensions.DurableTask v2.10.0. Using this setting with managed identity requires WebJobs.Extensions.DurableTask v3.x or later, or Worker.Extensions.DurableTask versions earlier than v1.2.x or later.|
 |useGracefulShutdown|false|(Preview) Enable gracefully shutting down to reduce the chance of host shutdowns failing in-process function executions.|
 |maxEntityOperationBatchSize(2.6.1)|**Consumption plan**: 50 <br> **Dedicated/Premium plan**: 5000|The maximum number of entity operations that are processed as a [batch](../articles/azure-functions/durable/durable-functions-perf-and-scale.md#entity-operation-batching). If set to 1, batching is disabled, and each operation message is processed by a separate function invocation.|
 |storeInputsInOrchestrationHistory|false|When set to `true`, tells the Durable Task Framework to save activity inputs in the history table. This enables the displaying of activity function inputs when querying orchestration history.|