It was an issue on the customer side. The application, obviously has a SQL Server backend, but it seems customers think databases just run themselves and don't require folks to work on them. They have no dedicated DBA resource. I provided this script to the customer as a way to fix an issue they were creating on their side. We have multiple customers using this application all over the world on this specific version that do not have this issue. Now if it was my database, that I managed, as a part of my SQL estate then yes I would agree, I should get to the root cause, but I am a "third-party vendor". I hope this better explains the issue.