Add configuration options for Activity Log Truncation to avoid timeouts

Fixed in

EPiServer.CMS.Core 12.2.0


Jun 10, 2020


Dec 17, 2021


CMS Core


Closed, Fixed and tested


The Activity Log truncation would frequently fail with the following error, so configuration options were added so that you can control the maximum number of activities that are removed, and specify a custom timeout for the database command execution.

One or more errors occurred. [Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]

You can now use the following settings in the ActivityOptions class in the Episerver.Cms.ActivityOptions section.

  • TruncateMaximum. Sets the maximum number of activities to remove.
  • TruncateDatabaseTimeout. Sets the timeout of the database command.