Hi @Rahul Banerjee ,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
The inconsistent behavior of the Blob storage-triggered Azure Function for different user groups may stem from several factors. One possibility is that the function's trigger is experiencing delays in processing changes made by User Group B. This could be due to the way the Azure Functions trigger monitors changes in blob storage. If the trigger isn't detecting changes from User Group B promptly, it may seem to work only when User Group A uploads files afterward.
- Moreover, if multiple Azure Functions are configured similarly, one function might inadvertently "steal" changes from another. This is especially relevant if both user groups are uploading files simultaneously, leading to potential conflicts.
To troubleshoot this issue, you might consider checking the following:
- Ensure there are no other Azure Functions with the same configuration that could be processing the same blobs.
- Investigate how long the function takes to execute to determine if it's causing delays in processing.
- Review the lease collection in the Azure Functions to confirm that there are no unexpected owners that could be affecting the processing of changes.
Also, for your better understanding, please refer to the following documentations:
If you find the answer helpful, kindly click "Accept Answer" and upvote it. If you have any further questions or concerns, please feel free to reach out to us. We are happy to assist you.