Bamboo "The plan has been disabled" in CI

By Kaveh Alemi·Latchkey

A disabled Bamboo plan does not build on commit or on schedule and cannot be run manually. Someone disabled it, or Bamboo disabled it automatically after repeated failures.

What this error means

Pushes do not trigger builds and the plan page shows "The plan has been disabled" or the run controls are greyed out.

The plan has been disabled.
No builds will be triggered until the plan is enabled.

Common causes

The plan was disabled manually

An administrator disabled the plan (for maintenance or while broken) and it was never re-enabled.

Auto-disable after repeated trigger or build failures

Bamboo can disable a plan whose repository trigger keeps failing, stopping it until the underlying issue is fixed.

How to fix it

Re-enable the plan

1. Open the plan and choose Enable (or Actions > Enable plan).
2. If it was auto-disabled, fix the failing trigger or repository first.
3. Trigger a manual build to confirm it runs.

# Plan > Actions > Enable plan
# or Plan configuration > Details > Enable

Fix the cause before re-enabling

If the plan auto-disabled from repeated failures, resolve the repository or trigger problem so it does not immediately disable again.

How to prevent it

• Track plan enablement so plans are not left disabled after maintenance.
• Fix failing triggers promptly to avoid auto-disable.
• Alert when a plan is disabled unexpectedly.

Frequently asked questions

Related guides

References

• GitHub Actions documentation