Pega Cloud enables the automatic large message exception handling feature by default. To make the feature available for an on-premises or client-managed cloud implementation, you must set up a large message repository and enable the feature by using dynamic system settings.

1. Configure a distributed repository using the Data-Repository Pega Platform class. The repository needs to be shared by all nodes in the cluster. Not all repository types apply. For example, you can use the file system repository type only if it points to a folder on a network drive that all the cluster nodes can access.
2. In the navigation panel, click RecordsSysAdminDynamic System Settings.
3. Click the following setting key and enter the name of your new repository:
   • Owning ruleset: Pega-Engine
   • Setting key: queueprocessors/largemessagesnapshot/repository
     Note: The default value is pegacloudfilestorage.
4. Click the following setting key and enter true:
   • Owning ruleset: Pega-Engine
   • Setting key: queueprocessors/largemessagesnapshot/enabled
     Note: The default value is false.
5. Click Save.
6. If necessary, you can change the default base path for the repository using the following setting key. This setting is not available in Dev Studio, however. For more information, see Editing a dynamic system setting.
   • Owning ruleset: Pega-Engine
   • Setting key: queueprocessors/largemessagesnapshot/basepath
   • Value type: string
   • Default value: queueProcessors/largeMessageSnapshots