Skip to content

Commit 8f33456

Browse files
Update blob-inventory.md
There is no option to generate a report retrospectively for a particular date. Highlighting this as part of known issues/limitation
1 parent da7c356 commit 8f33456

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/storage/blobs/blob-inventory.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -407,6 +407,8 @@ An inventory job can take a longer amount of time in these cases:
407407

408408
An inventory job might take more than one day to complete for hierarchical namespace enabled accounts that have hundreds of millions of blobs. Sometimes the inventory job fails and doesn't create an inventory file. If a job doesn't complete successfully, check subsequent jobs to see if they're complete before contacting support.
409409

410+
- There is no option to generate a report retrospectively for a particular date.
411+
410412
#### Inventory jobs can't write reports to containers that have an object replication policy
411413

412414
An object replication policy can prevent an inventory job from writing inventory reports to the destination container. Some other scenarios can archive the reports or make the reports immutable when they're partially completed which can cause inventory jobs to fail.

0 commit comments

Comments
 (0)