Skip to content

Release Update Studio Troubleshooting Issues


This section outlines some probable issues that can be encountered while using the Release Update Studio of the Lifecycle Experience Portal and the steps that can be followed to resolve those issues.

"Release Update Studio" button is not visible

There could be instances where the "Release Update Studio" button is not visible as depicted below;

Figure 1.1 - Release Update Studio button not visible

The above can occur due to two main reasons;

  1. The latest Release Update is already being applied to the Build Place, thus there is no requirement to navigate to Release Update Studio. Therefore, the button is hidden.

  2. When there is not a single 'approved delivery' from the Build Place. The Release Update will be based on the last approved delivery and when there is no such a delivery, the Release Update Studio button would be invisible.

Request Release Update Fails

A trigger on the "Check Status" button ideally sends a request to THOR to retrieve the latest status of the Request Release Update and once it's received, the status will be updated in the Release Update Summary table if it differs from the current status.

However, if the message: "Unable to update the Request Release status. Please try again." is populated as a toast message, this could be due to one of the two reasons listed below:

  1. Unable to retrieve the status from external system (THOR).
  2. Unable to update the Release Update Summary table with the status change.

At such an instance where the above toast message is displayed, please create a support issue and contact a representative of the IFS Support team to look into the issue.

Error in Impact Assessment/Impact Analysis

Figure 1.2 - Error in Impact Assessment/ Impact Analysis

Above error when opening the .upda file can be resolved by opening the customer solution repository once in web browser.

Customer Solution Repository Clone Failed in Update Analyzer

The error message as shown in Figure 1.2 is ideally occurred when the repository clones are not properly deleted due to one of the following reasons:

  1. When an unknown error occurs during the cloning or analysis process.
  2. When the Update Analyzer application is closed accidently or on purpose during cloning or analysis process.
Figure 1.3 - Failure in cloning the Customer Solution Repository

The usual behavior of the Update Analyzer tool is to delete all the cloned files, when closing the application. However, if repositories are partially cloned, the residual files need to be deleted manually prior to running the application again.

The following steps can be performed in such an instance to delete the residuals:

  1. Check the C drive and D drive for a 'UpdaClones' folder. Multiple folders can exist.
  2. Delete all.
  3. Re-open the .upda file to run the assessment or analysis.