29339

When a metric is registered to a very large number of resources (thousands), running business logic scope on the metric may fail with an internal error.

34711

32248

ACE2 doesn’t support the features below. There is no plan to support them in the future.

• Static Clustering
• Forecast
• Registration by event type

35645

There is a known issue in which migration of archived metrics from ACE1 to ACE2 fails.

To resolve:

Contact Support for a DB script to take the contract out of ACE2.

34125

ACE2 does not support the calculation of quick metrics.

To resolve:

Do not assign quick metrics to ACE2; by default their Contract Party is assigned to ACE1. Do not change the assignment.

36104

After a purge completes an entry is added each minute to t_purge_history, for all completed purges, until the job that runs at midnight cleans the table.

34818

When creating a new contract that contains a new metric and assigning a calculation policy that is different than the default one to the metric, the new calculation policy is overridden by the default calculation policy when performing a commit.

To resolve:

Assign the policy after the commit.

35611

When migrating metrics from ACE1 to ACE2 that were changed manually in the database to switch off granularities, errors are thrown during the calculation of the metrics.

32644

An archived contract is not calculated after an “Undo archive” action is performed when the data of the archived contract was purged.

N/A

When metrics assigned to ACE2 are later set to be forecast, they are not migrated back to ACE1 correctly.

To resolve:

First migrate the metric to ACE1, and then set it to be forecast.

N/A

The metric list does not show a registration error indication for metrics that include registration errors in the business logic module and therefore are not calculated.

To resolve:

Contact Support to receive a query that indicates such cases.

N/A

Contracts containing metrics that use uninitialized time zone names cause ACE2 to block all newly committed contracts even if the problematic metric is not committed.

To resolve:

Initialize the time zone names once the error occurs.

N/A

'Admin PSL - Data Purge - History' doesn't display data correctly and contains incorrect values following a raw data purge.