Skip to main content

Understand legacy lifecycle wizard downgrade warnings

Learn when and why the legacy lifecycle wizard is shown instead of the backend-driven wizard so you can flag potential configuration issues to your team.

Audience

This guide is designed for project manager.

Steps​

Step 1: Open a lifecycle in the wizard during development​

Open a lifecycle in the create or edit wizard in a non-production environment so that any downgrade warning banner, if applicable, can be displayed at the top of the page.

Open a lifecycle in the wizard during development

Step 2: Identify the legacy wizard downgrade banner​

Look for the amber warning banner with a triangle icon indicating that the legacy lifecycle wizard is being shown instead of the backend-driven configuration for the selected lifecycle.

Identify the legacy wizard downgrade banner

Step 3: Review which lifecycle is affected​

Read the first line of the banner to confirm which lifecycle code is currently running on the legacy wizard so you can reference it in conversations with your development team.

Review which lifecycle is affected

Step 4: Understand why the backend-driven wizard was skipped​

Read the detailed message in the banner explaining why the backend-driven configuration could not be used, and note this reason for follow-up with engineering or configuration owners.

Understand why the backend-driven wizard was skipped

Step 5: Decide next steps for project tracking​

Based on the downgrade reason, decide whether to raise a defect, create a technical task, or accept the legacy wizard temporarily while monitoring for a future backend-driven implementation.

Decide next steps for project tracking

Last updated: 2026-07-21