Welcome to Microsoft Q&A platform and thanks for posting your question here. This is indeed an unusual issue. Here are a few possibilities that might explain what's happening:
- Caching: Browsers like Microsoft Edge and Google Chrome handle caching differently. It's possible that Edge is caching the old version of the file, which is why you see the old version even after uploading a new one.
- Overwrite Issues: Azure Data Lake is not recommended for overwriting existing files. If you want to use the same filename and location, you can replace a file by overwriting it or delete the existing file and then upload.
- FileClient Settings: If you're using ADLS FileClient for uploading, you should set the Close option to true. Then the Storage Event will be sent yet another time after the upload stream was closed.
- Metadata Delay: There could be a delay in updating the metadata of the file in Azure Data Lake. You can consider using GetMetaData activity & If activity for achieving this.
- API Usage: If you're using an API for uploading the file, you should change position: currentLength to position: currentLength + fileSize in the Flush method. I would recommend trying to clear your browser cache or use an incognito window in Edge to see if that resolves the issue. If the problem persists, you might want to look into the other possibilities I mentioned. Hope this helps. Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue. Thanks