Thanks for getting in touch! I’m terribly sorry you’re hitting this unexpected and very annoying issue we’ve introduced. We reproduced it in 2018.6.9 and the fix for it was included in the next patch release (2018.6.10) and you can refer to the issue here.
Would you be able/willing to upgrade to at least that version (preferably the latest) and let me know if that fixes this behavior for you?
Let me know how you go or if you have any further questions moving forward.
Andrew from the Octopus Cloud team here. Yes I can certainly upgrade you to the latest Octopus version (we do run upgrades in the background, but they take some time to roll out across the fleet). I can see that you’re currently outside your maintenance window when upgrades will occur, so I can do one of the following:
If it’s OK with you, I can kick off an upgrade right now (or anytime), but you may experience a short outage while Octopus is updated; or
I can trigger it to occur during your next maintenance window (which should occur in about 18 hours)
If I don’t hear from you, I’ll set a reminder to get the upgrade kicked-off tomorrow during your window, and hopefully your problems will be resolved.
Sorry to keep you waiting, I didn’t catch your reply! This is all done for you, I triggered the upgrade on Saturday morning (my time) during your outage window as planned, so you should now be running 2018.6.14, and hopefully the issue is resolved.
If you do still find issues, post in here and I’ll dig in a little deeper .