We’ve seen this problem a couple times.
We have a quiet few projects that have auto release creation trigger configured. They work fine most of the times. However, if a user changes the name of the “package step”, the auto release creation stops working, and we see this message in server log:
"No release created for project ‘projectName’ when package packageName version 1.2.3 was pushed. No matching step could be found in the latest release. "
Is there a time latency between updating step name and Octopus picking up the change? or we need to remove/re-add trigger every time we update the step name. (Even though the “package step” already shows the new name)?
Any suggestions will be much appreciated!