Skip to main content

Troubleshoot lifecycle wizard downgrade warnings

Learn how to recognise when the lifecycle wizard has downgraded to a legacy configuration and what that means for your project setup.

Audience

This guide is designed for project manager.

Steps​

Step 1: Open the lifecycle wizard for your project​

Navigate to the project workspace and open the lifecycle wizard for the relevant lifecycle code (for example RAMS) so that the configuration can be loaded.

Open the lifecycle wizard for your project

Step 2: Wait for the lifecycle configuration to load​

Allow the wizard to contact the backend and attempt to load the effective lifecycle configuration, including any adapter-driven settings and overrides.

Wait for the lifecycle configuration to load

Step 3: Check for downgrade warning banners​

If the backend configuration cannot be resolved or the adapter build fails, look for a visible warning banner indicating that the wizard has downgraded to a legacy configuration.

Check for downgrade warning banners

Step 4: Confirm whether the legacy wizard is being used​

Review the wizard header or layout to confirm whether a legacy RAMS flow is being shown instead of the structured adapter-driven wizard.

Confirm whether the legacy wizard is being used

Step 5: Review console errors in a development environment​

In a development environment, open the browser developer tools console to see detailed [LifecycleWizardMount] error messages explaining why the downgrade occurred.

Review console errors in a development environment

Step 6: Decide whether to proceed with the legacy flow​

Based on the downgrade warning and console details, decide whether to continue using the legacy wizard for this session or pause and ask a technical owner to investigate the configuration issue.

Decide whether to proceed with the legacy flow

Last updated: 2026-08-11