In Salesforce Setup, search "Custom Metadata Types" and open it from the search results.

Click Manage Records next to the Log Settings entry.

In the Log_Settings list view, click Edit next to Default.

In the Log_Settings pane, the default values are:

1. Enable Logging is selected.

   This allows the Logging service to capture logs generated from the managed package. Select this option to capture logs for troubleshooting and support purposes.

2. Enable Pruning is selected.

   This allows the Log Pruning service to automatically delete log records when the Max Number of Logs value is reached.

3. Bypass Platform Events is not selected.

   When you select this option, Platform Events are bypassed when creating the record in the Log Object. Note that in this scenario, created records are rolled back when there are transaction failures. When you do not select this option, Platform events are triggered to write the record in Log Object. Do not select this option unless otherwise advised by your Medallia expert.

4. Log to System Debug is not selected.

   When you select this option, the Logging service also writes to debug logs while running a Debug Trace on a user account.

5. Max Number of Logs is set to 1,000.

   The maximum number of log records are retained at any given time. This can be tuned to your needs.

6. Interfaced Class Order is set to "LogToObject".

   Do not modify this setting. This functionality may change in a future release.

   

In Salesforce Setup, search Custom Settings and open it from the search results.

Click Manage next to Medallia Settings.

For new installations, click New.

For existing installations, click Edit.

Configure these parameters to manage the Queueing service:

1. Tab URL — Medallia Web reporting URL defined when enabling an iframe to Medallia reporting from the Salesforce UI. For existing installations, this field is already populated. See Enable experience reporting in Salesforce to learn more.

2. Record size — Use this setting to configure the queue size. Its default value is "10", which means each queue job will contain a maximum of 10 invitations. This setting ensures maximum compatibility with custom implementations, but it should be fine-tuned to the needs of each organization:

   1. If you notice there is a lengthy delay between Invitation creation and Invitations being sent to Experience Cloud, increase the record size value to process larger volumes for each queue transaction.

   2. If you know the average volume of Invitations that are generated per minute, increase the record size value to match; however, note that processing a larger number of Invitation records per job can reduce the overall time between the creation of Invitation records and when Invitation records are sent to Experience Cloud.

      Note: SFDC Apex CPU Time Limits apply to queue processing. If you experience an Apex-CPU-Time-Limit-Exceeded error during queue processing, reduce the record size value.

3. Add To Program Contact Fieldset — Determines the data payload that Medallia receives. For existing installations, this field is already populated. See Send data from Salesforce to Medallia to learn how to configure or modify this fieldset.

4. Number of Invitation Retries — Sets the number of times the Queueing service retries processing queue items. The default value is "5". After 5 retries, the queue item record is marked as "Failed" and the Queueing service does not retry to process the items in that queue item.

5. Minimum Queueable Delay in Minutes — Sets the minimum delay between queueable transactions. It allows the Queueing service to check queueable jobs against the Duplicate Signature Check class to ensure duplicate invitations are not created or sent. The default value (in minutes) is "1". Use higher values when duplicate invitations are being created.

   The value provided for this setting defines the period in minutes it takes the Queueing service to execute each queue item.

   Important: This also delays the sending of records from SFDC to Experience Cloud by the number of minutes defined for this parameter.

6. Notification Email Recipient — Enter the email address of a shared inbox or group email monitored by your Salesforce administrators to ensure queue processing error emails are not missed. By default, this value is null on both new installs and upgrade installs. When you do not enter a recipient, the default behavior is to send an email notification to the email address associated with the first administrator user found when querying users in the Salesforce org.

7. Queue Processing — This parameter controls whether the queue processor is active and processing queue item records through to the Medallia API endpoint. When it is unchecked, queue processing is inactive and no records are sent to Medallia. On new installs, the default value is set to “True”. On upgrade installs, the value is “False” and must be changed to "True" to process the invitation queue.

Click Save.

Navigate to the Medallia Setup app from the App Launcher.

Click Restart Queue Processing.

Create a batch class.

Open the Developer Console, select New, then select Apex Class.

Paste the code below into the code editor.

global class MedalliaDeleteQueueItemBatch implements Database.Batchable<SObject> {

  // Select all medallia_xm__QueueItem__c records
  global Database.QueryLocator start(Database.BatchableContext BC) {
    return Database.getQueryLocator('SELECT Id FROM medallia_xm__QueueItem__c');
  }

  // Batch the record deletion operation
  global void execute(Database.BatchableContext BC, List<medallia_xm__QueueItem__c> scope) {
    try {
      // Delete records
      Database.delete(scope, false);
    } catch (Exception e) {
      // Log Error
      System.debug('Error deleting records: ' + e.getMessage());
    }
  }

//Finish method after all batches process
  global void finish(Database.BatchableContext BC) {
    System.debug('Batch processing completed.');
  }
}

Click Save.

Open the Developer Console.

Open the Debug > Execute Anonymous screen.

Paste the code below into the code editor.

MedalliaDeleteQueueItemBatch delBatch = new MedalliaDeleteQueueItemBatch(); Database.executeBatch(delBatch, 200);

Click Execute.

Open the Developer Console.

Open the Debug > Execute Anonymous screen.

Paste the code below into the code editor.

List<medallia_xm__QueueItem__c> queueItems = [SELECT Id FROM medallia_xm__QueueItem__c LIMIT 10000];
     
    if (!queueItems.isEmpty()) {
      try {
        delete queueItems;
        System.debug('Deleted ' + queueItems.size() + ' queue items.');
      } catch (DmlException e) {
        System.debug('An error occurred: ' + e.getMessage());
      }
    } else {
      System.debug('No queue items found to delete.');}

Click Execute.