Hey @rik.crompton,
Thank you for your patience whilst I looked into this.
I was able to confirm that the config as code projects not showing in the step template usage tab is a bug, but is not related to the issue you’re experiencing as no one else has reported it.
For reference, you can see the GitHub issue here: Config as code - step template usage not updating · Issue #7399 · OctopusDeploy/Issues · GitHub.
I couldn’t find anything that looked strange or out of place in the database via SQL queries or through digging into API requests.
I even tried recreating the issue on our own servers, by linking a CaC project to a step template multiple times in one deployment process, to see if that caused any issues, but they all updated as expected.
Just to ask again for explicit permission, are you happy for us to try to update and commit the step template inside the SIP project for branch 17390_CheckForSqlConnectionLeak?
This is so that I can also instruct our devs who may decide to explore the instance further to see if they can spot anything.
And to eliminate any confusion, you’re saying that if you do not update the step template and make a different change to the same project in the same branch, that you can update and commit those changes without any errors occurring?
Kind Regards,
Adam