Thank you for confirming that, I just wanted to make sure your permissions were correct.
In a previous response in this thread Brent mentioned another user was having this issue. He was having it at schema version 4 though, not 3 like you are on. A private issue was created by the engineers for that which is still being looked into.
I asked you to perform the workaround in that private issue, however, this did not work for you as your schema version was still set to 3 even though you changed the template, meaning a forced schema update to 4 or 5 should have been done.
Since you are on 2022.2 I think you will be stuck on schema version 3. I know I had to upgrade my instance to a 2022.3 version to be able to update my CaC schema version so it may be the workaround will not work for you since changing templates wont force an upgrade unless you upgrade Octopus.
I am going to try and get the engineers to create a public GitHub issue for this so you can subscribe to it and view it fully.
In the private issue a note has been posted in it saying:
What’s happening is that the endpoint used to update the templates (
api/Spaces-1/actiontemplates/ActionTemplates-41/actionsUpdate ) doesn’t have a project ID or git ref, so the action filter won’t automatically add anything to the
IProjectScope . When it’s time to commit the git transactions, we no longer have anything in the
IProjectScope , hence the
Stack empty. exception message.
This lines up with what the engineers are seeing in your HAR file so I do now think your issue is the same as the one in the forum post I linked. The private issue specifically mentions schema v4 that has the issue thats all so unfortunately that threw me off at the start.
Unfortunately the workaround will not work for you so I am going to go back to the engineers with the following:
Ask them to create a public GitHub issue for this so its visible to users.
Get them to update the issue to incorporate v3 schemas.
Get them to see if there is another workaround in place for customers who are unable to upgrade to v4.
It may be that the only way to get you unstuck here is to upgrade your octopus instance to a 2022.3 version so you are able to upgrade your schema and perform the workaround but I will see if our engineers have a better alternative first.
I am sorry this has gone on so long and we have ended up circling back around to the original response but hopefully I can get somewhere with the engineers over the next few days and have an answer for you.
Reach out in the meantime if you need anything else,