Here you will find information about:

• limitations,
• known issues,
• changes in the supported environments,
• any unexpected behvavior of Optimize (e.g due to a new feature)

Known issues

Broken Links

After the migration it might be possible that you encounter weird errors in Optimize:

• Buttons or links are not working when you click on them.
• You get errors in your web browser when you open the Optimize page.

In this case please clear your browser cache, so that your browser loads the new Optimize resources.

Broken raw data reports

Apart from caching issues there is the following list of known data upgrade limitations:

• Raw data reports with custom column order are broken showing the following error when opened:

    Cannot read property 'indexOf' of undefined
  

  To resolve this either delete and recreate those reports or upgrade to 2.4.0 which resolves the cause.

• Combined reports might cause the reports page to crash with the following error

      Oh no :(
      Minified React error #130; visit http://facebook.github.io/react/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
  

  To resolve this issue, you need to upgrade to 2.4.0 straight away.

Misinterpreted cron expressions

The configuration of Optimize allows you to define when the history cleanup is triggered. For that, the Cron expression notation is used. However, the values are incorrectly interpreted in Optimize. For example, the historyCleanup.cronTrigger configuration has the default value 0 1 * * *, which should be 1am every day. Unfortunately, a bug causes this to be interpreted as every hour.

To fix this just use the spring cron expression notation. For instance, the default value for historyCleanup.cronTrigger would then be 0 0 1 * * *.