I have a .Net Project that has integrated Sentry.io logging. Basic Exception handling over an API call(if api call and deserialization fails). The repo, build and release pipelines lives in Azure Devops
I saw thousands of errors coming through and thought it was my app running in IIS that caused this but I noticed that the source of the error was a path that looks like devops (D:\a\1\s...).
The errors only stops if I remove the exception handling and build/release it. To test my theory (after it stopped) I added the error handling back in and rereleased the latest build and it started again. (My release pipeline only extracts files, stops IIS, transfer files, start IIS)
Any idea what could be causing this/avoid it happening in the future?
Edit: I added a step in to delete the extracted files but this doesn't solve the issue
Even though I have a private release agent on my server. The error path is on par with files hosted in Azure Devops and not on my server