Skip to content

Incident detail

Manual intervention steps on Configuration-as-code projects may throw errors

Resolved incidentMajor

Timeline window

to

Get alerted the next time Octopus Deploy breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    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

  2. Identified

    We have identified the root cause of this issue and are working on a hotfix build.

  3. Monitoring

    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.

  4. Resolved

    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 support@octopus.com.

Keep exploring

More from Octopus Deploy

Neighboring incidents on Octopus Deploy's timeline and the rest of their record on OutageDeck.