Skip to content

Commit 7151b73

Browse files
committed
Mark large payload docs as preview
1 parent 6f474ff commit 7151b73

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-large-payloads.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Large payload support with Durable Task Scheduler
3-
description: Learn how to use large payload support in Durable Functions and the Durable Task SDKs with Durable Task Scheduler and Azure Blob Storage.
2+
title: Large payload support with Durable Task Scheduler (Preview)
3+
description: Learn how to use preview large payload support in Durable Functions and the Durable Task SDKs with Durable Task Scheduler and Azure Blob Storage.
44
ms.topic: conceptual
55
ms.date: 03/14/2026
66
ms.author: torosent
@@ -10,7 +10,7 @@ ms.devlang: csharp
1010
zone_pivot_groups: azure-durable-approach
1111
---
1212

13-
# Large payload support with Durable Task Scheduler
13+
# Large payload support with Durable Task Scheduler (Preview)
1414

1515
Large payload support lets your app pass orchestration inputs and activity outputs that exceed the [Durable Task Scheduler](durable-task-scheduler.md) message size limit. When a payload goes over the configured threshold, the framework stores the serialized payload in Azure Blob Storage and sends a small reference through Durable Task Scheduler.
1616

@@ -299,6 +299,9 @@ The sample apps also validate the round trip:
299299

300300
Because the runtime stores externalized payloads with gzip content encoding, Azure reports the compressed on-disk blob size. With the current low-compressibility sample payloads, those blob sizes should stay reasonably close to the logical payload size.
301301

302+
> [!NOTE]
303+
> Purging orchestration instances doesn't currently delete the corresponding externalized payload blobs from Azure Blob Storage. If you need to remove those payloads, delete the blobs from the storage account separately.
304+
302305
## Next steps
303306

304307
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)