Is there a possibility that old scripts/bindings can still be running after they’re overwritten by a commit?
Some spooky backstory:
This may sound strange, but I’ve had an SQL query binding on a component in a template that was locking database resources in MsSQL. I checked the active processes in the Activity Monitor, and found a single connection acting as a head blocker, holding up multiple other processes. So I checked the details of the process for the query contents, and ran a project-wide scan to locate its origin. The search results indicated that the instruction originated from a numeric text field binding inside of a template. However, when I checked the template binding I found that the contained query is different (fixed in other words).
Screenshot of the Activity Monitor:
Screenshot of the search results:
Screenshot of the binding window:
This is made even more strange by the fact that this project has been backed-up and restored to a new gateway since the change was made. The version of the Gateway is 7.9.4. A coworker of mine also claims that an old tag-change event script was littering our logs for weeks after he committed a change that removed it. Has anyone seen such trickery before, or could something else be happening that I don’t see?
Any help with this mystery would be greatly appreciated!