If the configuration (profiles, environments, agent appings) is changed, the CMR's AbstractConfigurationChangeListener, which starts the jobs to update the configuration, times out if the update requires more time than 1 minute.
In case, the update takes very long (e.g. huge class base), the CMR is not able to finish the configuration change because of the timeout. This behavior (timeout duration) should be configurable that the user can increase or adapt the timeout, e.g. if the target application shows a high amount of classes.
Furthermore, the UI freezes during the update process. Thus, if the configuration change takes much time, the UI is not responsive until the CMR finishes the job or throws the 1 minute timeout.