Now I got it:-
Polling and latency
Polling works as a hybrid between inspecting logs and running periodic container scans. Blobs are scanned in groups of 10,000 at a time with a continuation token used between intervals. If your function app is on the Consumption plan, there can be up to a 10-minute delay in processing new blobs if a function app has gone idle.
Solutions:-
If you require faster or more reliable blob processing, you should instead implement one of the following strategies:
- Change your binding definition to consume blob events instead of polling the container. You can do this in one of two ways:
- Add the source parameter with a value of EventGrid to your binding definition and create an event subscription on the same container. For more information, see Tutorial: Trigger Azure Functions on blob containers using an event subscription.
- Replace the Blob Storage trigger with an Event Grid trigger using an event subscription on the same container. For more information, see the Image resize with Event Grid tutorial.
- Consider creating a queue message when you create the blob. Then use a queue trigger instead of a blob trigger to process the blob.
- Switch your hosting to use an App Service plan with Always On enabled, which may result in increased costs.
It's mentioned in the documentation itself https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=in-process%2Cextensionv5&pivots=programming-language-python
If you have suggestions, welcome.