Downgrading Systems

The buttons for upgrade or downgrade buttons are located in the user systems section, particularly within the version history tab.

Step 1: Initiate the Downgrade

To begin the downgrade process, click the Downgrade button available for that particular system.

Only one upgrade or downgrade can be done at a time. Downgrading is not allowed from the default or current version and is only possible if the version was upgraded from an earlier one.

Step 2: Review Changes and Release Notes

Upon clicking Downgrade, a screen will display the release notes and list of changes for the previous version. Carefully review this information.

By clicking Next, Users will be advancing to the Pre-Check Validation..

Pre-Check Validation

Before proceeding further, the system performs the following pre-checks:

• No project transfer should be in progress.

• No other upgrade/downgrade process should be active for the same system in the same project.

If any check fails, an appropriate error message will be shown and the process must be restarted.

Once all checks pass, the Next button is enabled.

Step 3: Disable Workflows & Deleted API Usage (Optional but Recommended)

Users will be prompted to disable all workflows currently using this system to ensure smooth transition.

Click Disable all now to proceed. A confirmation pop-up will appear.

• The system displays a list of deleted APIs and the workflows where they're used.

• Click the arrow icon next to any workflow to open it in a new tab.

If no deleted APIs are present, Users can proceed by clicking Next.

If the workflow is modified in a different tab, changes (such as a deleted API or a disabled alert) will appear only after switching to the respective tab in the upgrade modal or refreshing the page.

Step 4: Kill Running Jobs

The next step shows a list of all running jobs for the current system version.

Click Kill Now to stop all running jobs. A confirmation pop-up will be displayed.

Once all jobs are successfully terminated, proceed to the next section.

If the workflow is modified in a different tab, changes (such as removal of a processing and queued jobs) will appear only after switching to the respective tab in the upgrade modal or refreshing the page.

Step 5: Final Confirmation and Downgrade

Users now see the final confirmation screen.

On clicking Downgrade, the system performs a final check for deleted APIs in use, running or queued jobs, and enabled workflows. If any check fails, the downgrade is aborted and must be restarted from the beginning.

Lock-in Period

If no action is taken on the final screen, a one-hour lock-in period begins to prevent consequences or interruptions. During this time, no upgrade or downgrade can be triggered for the same system. After one hour, the upgrade/downgrade option is re-enabled.

Enable Workflows After Downgrade

Once the downgrade is completed, click Enable All Workflows to re-enable only those workflows that were active before the downgrade.

If this step is skipped and the window is closed, Users must manually enable the required workflows later. It is highly recommended to test one or two workflows before enabling all workflows.