Octopus incident
Manual intervention steps on Configuration-as-code projects may throw errors
Resolved after 3 days 7 hours, on November 13, 2023.
This incident has been resolved. A public incident report will be made available to affected customers. If you would like a copy, please get in touch with us at [email protected].
Update timeline
- investigating Nov 13, 2023, 07:32 PM UTC
We are investigating reports of Octopus Cloud users on 2024.1.746 having issues in the follow scenario: * Configuration-as-code projects with a Manual Intervention step, with the "Responsible team" set to a System-level team. More details including a possible workaround can be found in the following GitHub issue: https://github.com/OctopusDeploy/Issues/issues/8473
- identified Nov 13, 2023, 08:29 PM UTC
We have identified the root cause of this issue and are working on a hotfix build.
- monitoring Nov 14, 2023, 03:52 AM UTC
We are now in the process of rolling out a version containing a fix to resolve the issue. This will be available to affected customers and we will be monitoring for any further issues.
- resolved Nov 17, 2023, 03:22 AM UTC
This incident has been resolved. A public incident report will be made available to affected customers. If you would like a copy, please get in touch with us at [email protected].
Your product runs on more than Octopus
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services