Compatibility issues in runbooks are not reported when converting to version control

[geofflamrock]

Severity

At least one report, workaround in place

Version

2026.1.11242, likely earlier from when support for runbooks was released in CaC projects

Latest Version

I could reproduce the problem in the latest build

What happened?

When converting a project to use version control, there are a set of compatibility checks that are done, including:

• When sensitive values are used in a deployment process directly (not through a variable).
• When step templates being used in a deployment process are no longer available.

Any issues from these checks are shown in the Version Control page in a project, and must be fixed before converting the project to use version control.

Runbooks are currently not considered in these compatibility checks, resulting in errors during conversion which are hard to understand or subsequent failures when running runbooks.

Reproduction

• Create a project
• Create a runbook
• Add a step to the runbook which supports setting a sensitive value directly (e.g. Deploy a certificate to Tomcat) and save with the sensitive value
• Go to Version Control settings page for the project

There won't be any compatibility issues shown, clicking the Convert button will result in an error similar to Failed to execute migration 1: Can not write sensitive values to OCL

Error and Stacktrace

More Information

No response

Workaround

• Change any sensitive values in runbook processes to use variables.
• Ensure that any step templates used in runbook processes exist.

[octoreleasebot]

Release Note: Include runbooks in compatibility checks when converting a project to use version control

[team-builds-bot]

🎉 The fix for this issue has been released in:

Release stream	Release
2026.2	2026.2.5874