In SAS Marketing Automation, a change in the schedule of a campaign results in the Campaign Occurrence numbers being reset to 1. From the next campaign execution, the contact history starts to be overwritten. When you change the schedule of a Campaign Group, the schedule for all campaigns in the group changes.

You can work around this problem by creating a new reporting version of the campaign. A new reporting version has occurrences correctly starting from 1. Reporting on Contact History is more complicated when campaign versions need to be considered.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, the following new JVM argument is available:

The default for this option false. You should set this argument to true in your application server start-up script where sas.custintelcore is deployed, which is typically SASServer6. In order for the change to be effective, you will need to restart the server after this update.

With this new JVM argument, a change in functionality occurs when a previously executed Communication node with existing executed occurrences is rescheduled. The existing occurrence list of the Communication node contains only the already executed occurrences. The occurrence list for the new schedule is appended to this list. The first execution under the new schedule starts at N+1, where N is the occurrence number of the most recent execution under the old schedule, including any manual execution.

Note that only Communication nodes have occurrence lists. Even when campaign- or group-level scheduling is used, only the Communication nodes have occurrence lists. This is because only Communication nodes execute in the sense of creating exports and updating the common data model.

Changes to the occurrence list are made when the user clicks OK out of the scheduling dialog box after having modified the schedule, NOT when the schedule is sent to Schedule Manager.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 5.4_M1 is available at:

A fix for this issue for SAS Marketing Automation 5.41 is available at: