Observed on nightly demo:

• Activate cache statistics in cms admin configuraiton
• Use the derby data source (default)
• In front admin configuration, the cache statistics are activated
• The monitoring datasource is "DO NOT SELECT OR USE Back-office Synchronized Datasource (Derby Ametys)"

Cache stats are updated every hour at XX:15

During this update I have errors (one on back cache stats update and the other one on front cache stats update).

See attached files