We have had this issue for some time now, but as it wasn’t critical I hadn’t reported it, thinking it would just get resolved over time. I can see the same issue was logged back in January, with a link to GitHub issue https://github.com/OctopusDeploy/Issues/issues/2801, which was marked as going out in 3.8.9. However, we still see this issue up to the latest release, 3.15.3. Any idea why this is still occurring? It’s more of a nuisance than anything else.
Cheers, Simon.
Hi Simon,
Thanks for getting in touch! This issue was quite annoying, I personally have not seen it since 3.8.9 and I just tested this in a couple of script areas in Octopus using 3.15.3, I was unable to replicate this behavior though. Would you please be able to provide some more information regarding where you are seeing this in Octopus?
Is it all script steps or just certain steps?
Some steps for me to reproduce this on my end will be helpful, I can then pass it onto the develops once its easily replicated.
It could potentially be helpful to get an output of any errors in your web browsers developer console while this happens.
Looking forward to hearing from you. 
Best regards,
Daniel
Hi Daniel - Thanks for the reply. We are seeing this in all of our script steps, and have been for a few months now. We have three parent steps, each with several child steps, and this message appears on every step, we have import cert steps, Powershell steps, Azure Powershell steps, package deployment steps, email steps, even the manual intervention step raises the message. As soon as you enter the step the top right corner says “You have unsaved changes”, and if you navigate away the attached message displays.
I’ve attached the messages received in the Chrome console, there are a couple of messages in there that may help…
Cheers, Simon.
Dev_Console_Messages.txt (10 KB)
This may also help - In order to troubleshoot this, I created a new project with a single step, using the Manual Intervention template. This worked fine. Then I added a Run Condition to the step. Now, as soon as I access this step, the issue occurs. Each of the three parent steps in our project has a run condition defined, it looks like this must be the culprit…
Further to this, if I remove the Run Condition, the error still persists, and I tried this on our main project as well. Even after removing the run condition, if you add one back in it seems to remember the variable you used previously, so it doesn’t seem to completely remove it???
I can confirm this because the step definition in the database looks like this, after I removed the run condition:
{
"Steps": [{
"Id": "b540c5e2-4711-4795-815b-39e5b32d9c12",
"Name": "Run a script",
"Condition": "Always",
"StartTrigger": "StartAfterPrevious",
"RequiresPackagesToBeAcquired": false,
"Actions": [{
"Id": "a6aab97a-d67e-443c-98f3-12f7743516a7",
"Name": "Run a script",
"ActionType": "Octopus.Script",
"IsDisabled": false,
"Environments": [],
"ExcludedEnvironments": [],
"Channels": [],
"TenantTags": [],
"Properties": {
"Octopus.Action.RunOnServer": "false",
"Octopus.Action.Script.Syntax": "PowerShell",
"Octopus.Action.Script.ScriptSource": "Inline",
"Octopus.Action.Script.ScriptBody": "Write-Host \"This is my only deployment step!\"
}
}],
"Properties": {
"Octopus.Action.TargetRoles": "Deploy CLS",
"Octopus.Action.ConditionVariableExpression": "#{Octopus.Action.Azure.AppOffline}"
}
}]
}
Note that the ConditionVariableExpression value is still present, even though the Condition is set to Always.
Hi Simon,
Thanks for the info here! It looks like it’s the run condition variable doing this. I have just created a GitHub issue to look into this.
You can following the issue here: https://github.com/OctopusDeploy/Issues/issues/3662
Thanks again for the info here, it will surely help the devs resolve this.
Best regards,
Daniel