Skip to content
OutageDeck

Incident detail

Bicep deployments may fail after upgrading to 2026.3.4658 or later

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.

Set up free alertsHow Octopus Deploy alerts work

Timeline

Incident updates

Every update Octopus Deploy posted, oldest to newest, exactly as it appeared on their official status page.

  1. Identified

    We have identified an issue in Octopus Server 2026.3.4658 or later when existing Bicep deployments may start failing.

    We have a public issue tracking this with a workaround https://github.com/OctopusDeploy/Issues/issues/10129

    We are working on a fix and will update this incident and the public issue when it's resolved.

  2. Resolved

    The fix has been live across all Octopus Cloud servers for several weeks now without further issues.

Keep exploring

More from Octopus Deploy

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

← Older incident

Ability to deploy in West US 2 might be affected

Newer incident →

Service connectivity issues due to upstream Azure outage

All Octopus Deploy incidentsOctopus Deploy live status