I'm glad to hear you solve the problem ,if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.
By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others.". and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:
[Unable to delete a document in a SharePoint Online document library - etag mismatch]
Issue Symptom:
We have a metadata driven document library and we are unable to delete a file. When you attempt to delete the file, you receive this error message: The resource has changed since the caller last read it; usually an eTag mismatch. This document library also has a flow that we use to approve publishing a document.
I re-ran, successfully, the publishing flow - did not help
I deleted all drafts and versions of the file that I could thru Version history - did not help
Opening the file shows no one else editing the file
Was able to successfully rename the file
Confirmed no issue deleting other files in the library
Waited a day or two to see if any locks needed to be cleared - no help
Searching for an error like this did not return any results that are related to these circumstances.
Reviewing the history of the approval flow - as far back as the 28 days that is saved, I don't see an instance of the flow that is still running on that file.
What could be holding the file so it can't be delete.
Current status:
I did find a way to delete the file. I disabled my custom publishing flow and manually published the file. This allowed me to delete it.
You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.