Has autodeployment from triggers stopped working properly?
Our projects which have all been working are suddenly failing to auto deploy. However as soon as I start a deployment manually then the automatic one seemed to kick in and mine was behind it in the queue.
Everything looks good on the setup (it hasn’t changed in ages) and I can see there is an updated package in the library but for some reason the autodeploy hasn’t triggered. This is the case for at least 3 of our projects, all of which were working up to yesterday.
Hey @darren.woodford,
As our banner suggests we do not actively monitor these forums any more and you are on our Cloud Legacy version so are only entitled to community support through these forums but I was alerted to this by another customer who is experiencing the same issue.
We love to help our customers and since we already know about this I wanted to come on here and mention it to try and get you working again. It may also help other customers running into this at the moment.
I took a look at your logs and your instance is experiencing the same issue as the other customer:
It does look like you are running into this known GitHub issue -
Automatic release creation unable to set versioning strategy and failing · Issue #8423 · OctopusDeploy/Issues · GitHub.
The fix is out for this in 2023.4.7548 , your instance is currently on 2023.4.7210 . Would you be happy for me to schedule an upgrade to 2023.4.7608, which is the next release we have out for Cloud, and see if that fixes your issue?
I can either schedule the upgrade for now (this will require around 20 to 30 minutes downtime), or I can schedule it to run during your next maintenance window 02:00 - 04:00 (+01:00).
Let me know which one you would prefer and I will schedule that for you, I am sorry you have run into this bug.
Kind Regards,
Clare
Hi Clare
Thanks for your assistance on this and acknowledging the bug. At least I can stop trying to resolve it myself now. We will wait for the automatic update to 7385+ as I don’t want to risk other bugs especially with the limited testing on 7399 to date and our current unsupported state. I know the bug exists and I can easily deploy manually for now. One of your colleagues has supplied us with a quote for upgrading to Professional which I am hoping to get signed off this week which should make things easier.
Any idea when testing will be completed for 7399 and it will be automatically rolled out to us please? I have just checked our version and it seems we are now on 2023.4.7210.
Regards
Darren
Hey @darren.woodford,
Thank you for replying - did you manage to re-read my initial comment at all as I unfortunately had to edit it about 45 minutes ago as our engineers made a mistake with the version number the fix is in.
The fix is now in 2023.4.7548 , your instance is currently on 2023.4.7210.
We have the version 2023.4.7608 available to put customers on and we currently have 59 customers on that with no issues to date.
I have just upgraded one customer to see if that resolves their auto trigger issue so will let you know if it does but would you like me to put your instance on 2023.4.7608 now (20 to 30 minutes downtime) or during your next maintenance window (01:00 - 03:00 (+00:00) — starts in 15h 44m)
Your instance is on the 2023.4.7210 branch so it will be a few weeks before you get pushed to 2023.4.7608 or higher but if you are happy to wait for then I can just leave your instance to auto-upgrade as part of our usual schedule.
Let me know what option you want to take and I will be happy to schedule the upgrade or leave it for now.
Great news about the professional license, we will look forward to supporting you along your Octopus journey!
Kind Regards,
Clare
Hey @darren.woodford and any other customer reading this,
Just to let you know the other customer that had this issue was upgraded to 2023.4.7608 and his triggers are now working again so if you are having this issue and you are on an active Octopus license please reach out to support@octopus.com and we can get you upgraded to that version if you are not on it already.
Darren, let me know what you want to do with your instance and I can go about actioning that for you to get this resolved if you would like?
Kind Regards,
Clare
Hi Clare
Sorry, I only read the email notification and didn’t realise you had edited the response. Thank you for the update and additional research. Yes please upgrade our instance to 7608 with immediate effect.
Kind regards
Darren
Hey @darren.woodford,
Thank you for confirming you would like your instance upgrading to 2023.4.7608 immediately. I have just gone ahead and run that task so you should see your instance go down for maintenance in the next few moments.
I will message you on here as soon as it comes back online and you can then test your triggers if you are able to.
Kind Regards,
Clare
Hey @darren.woodford,
Your instance is now back online and has been upgraded to 2023.4.7608. Hopefully your auto triggers should now work!
Once you have upgraded to Professional you are welcome to email us with any questions or concerns at support@octopus.com.
Thank you for your patience whilst we looked into this for you,
Kind Regards and Happy Deployments,
Clare
Autodeployment is working again now, thanks Clare.
P.S. It might be an idea for you to fix my typo in the subject (Autdeployment → Autodeployment) to help others find this topic. I have tried but I can’t see a way to change it.
Hey @darren.woodford,
Great news you can now autodeploy again, I am glad the upgrade worked for you and that I could help!
I can also see you managed to fix the title of the forum post too so thank you for that!
Kind Regards,
Clare
I can also see you managed to fix the title of the forum post too so thank you for that!
I didn’t but according to the edit history @dan_close did 
Hi Clare
Autodeployment failed on one of our projects again yesterday. If you look at the “Artwork Approval” project in our instance you will see that version 1.1.99.0 is the last version deployed to Dev environment however there is a version 1.1.100.0 in the library despite having a trigger set on the Deploy Server stage.
Regards
Darren
