Disable automatic pruning and remove the persisted schedule configuration.

Retrieve the configuration of waiting for commitments from counter-participants Participants that have been removed from the topology will still be visible in the list until they are removed from the no wait configuration.

Retrieve the automatic, participant-specific pruning configuration.

Retrieve the safe pruning offset

Retrieve the automatic pruning configuration.

Prune the participant specifying the offset before and at which ledger transactions should be removed. Only returns when the potentially long-running prune request ends successfully or with one of the following errors: - INVALID_ARGUMENT: if the payload, particularly the offset is malformed or missing - INTERNAL: if the participant has encountered a failure and has potentially applied pruning partially. Such cases warrant verifying the participant health before retrying the prune with the same (or a larger, valid) offset. Successful retries after such errors ensure that different components reach a consistent pruning state. - FAILED_PRECONDITION: if the participant is not yet able to prune at the specified offset or if pruning is invoked on a participant running the Community Edition. Note that this endpoint only prunes the Canton stores not the ledger API stores. For the latter, use the pruning service on the ledger API. This limitation only applies to this endpoint, the other endpoints in this service, most notably the ones for scheduled pruning prune all stores.

Enable waiting for commitments from the given counter-participants Waiting for commitments is the default behavior; explicitly enabling it is useful if it was explicitly disabled

Modify individual pruning schedule parameters. - INVALID_ARGUMENT: if the payload is malformed or no schedule is configured

Disable waiting for commitments from the given counter-participants Disabling waiting for commitments disregards these counter-participants w.r.t. pruning, which gives up non-repudiation for those counter-participants, but increases pruning resilience to failures and slowdowns of those counter-participants and/or the network

Enable automatic pruning with participant-specific schedule parameters.

Enable automatic pruning using the specified schedule parameters The following errors may occur on the SetSchedule or Update commands: - INVALID_ARGUMENT: if a parameter is missing or an invalid cron expression or duration. - FAILED_PRECONDITION: if automatic background pruning has not been enabled or if invoked on a participant running the Community Edition.