Merge pull request #299537 from sshankMSFT/docs-editor/storage-task-known-issues-1746721997

Update storage-task-known-issues.md

Author: prmerger-automator[bot]

articles/storage-actions/storage-tasks/storage-task-known-issues.md

@@ -30,16 +30,6 @@ During the public, you can target only storage accounts that are in the same reg
 
 Azure Storage Actions autoscales its processing tasks based on the volume of data in a storage account, subject to internal limits. The duration of execution depends on the number of blobs in the storage account, as well as their hierarchy in Azure Data Lake Storage Gen2. The first execution of a task over a path prefix might take longer than subsequent executions. Azure Storage Actions are also designed to be self-regulating and to allow application workloads on the storage account to take precedence. As a result, the scale and the duration of execution also depend on the available transaction capacity given the storage account's maximum request limit. The following are typical processing scales, which might be higher if you have more transaction capacity available, or might be lower for lesser spare transaction capacity on the storage account.
 
-In a 14 day period, Azure Storage Actions can process 90 billion blobs in an account that has a flat namespace, and 7 billion blob in an account that has a hierarchical namespace.
-
-## Premium Block Blobs 
-
-Creating assignments on PBB storage accounts doesn't work. Will be fixed in STG100. 
-
-## Soft deleted blobs are included in listing during scanning as objects targeted 
-
-Exclude the prefix.
-
 ## Billing doesn't show task assignment name 
 
 Billing meters show up on the bill with only the storage account name. Subscription bill doesn't show the task assignment name for which the meter was emitted. To correlate the meter with the task assignment, you must look at the resource metrics for Storage Actions filtered by the storage account for that day.
@@ -113,6 +103,14 @@ Task assignments must be cleaned up before moving storage accounts across resour
 
 If during the assignment process, you assign a role which doesn't have the required permission, the storage task run will take 14 days to fail. To unblock the task run, you can add the required role to the managed identity of the storage task. Otherwise, the task assignment will be stuck in the **in progress** state until the task run ends in 14 days.
 
+## Premium Block Blobs 
+
+Creating assignments on premium block blobs storage accounts doesn't work.
+
+## Soft deleted blobs are included in listing during scanning as objects targeted 
+
+The workaround is to exclude the specific prefixes which are soft deleted.
+
 ## See Also
 
 - [Azure Storage Actions overview](../overview.md)