Skip to content

Commit 9f6987b

Browse files
authored
Add information on blobscaninfo LatestScan for blob triggers
This commit adds a section explaning where to find the *scaninfo* file and how to change it to force an immediate rescan of the blob storage. Ref #MicrosoftDocs/azure-docs#50660
1 parent ed6b713 commit 9f6987b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/functions-bindings-storage-blob-trigger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -386,7 +386,7 @@ Azure Functions stores blob receipts in a container named *azure-webjobs-hosts*
386386
* The blob name
387387
* The ETag (a blob version identifier, for example: "0x8D1DC6E70A277EF")
388388

389-
To force reprocessing of a blob, delete the blob receipt for that blob from the *azure-webjobs-hosts* container manually. While reprocessing might not occur immediately, it's guaranteed to occur at a later point in time.
389+
To force reprocessing of a blob, delete the blob receipt for that blob from the *azure-webjobs-hosts* container manually. While reprocessing might not occur immediately, it's guaranteed to occur at a later point in time. To reprocess immediately, the *scaninfo* blob in *azure-webjobs-hosts/blobscaninfo* can be updated. Any blobs with a last modified timestamp after the `LatestScan` property will be scanned again.
390390

391391
## Poison blobs
392392

0 commit comments

Comments
 (0)