SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 55326: Re-executing a communication in SAS® Customer Intelligence after a failed execution does not update the COMMUNICATION_OCCURRENCE_NO table correctly

DetailsHotfixAboutRate It

Re-executing a communication in SAS Customer Intelligence after a failing execution of the campaign will not update COMMUNICATION_OCCURRENCE_NO correctly.

To re-create this situation, follow these steps:

  1. Create a simple campaign by selecting Select Node ► Cell Node ► Communication Node ► Custom Diagram Tools.
  2. Execute the campaign.
  3. The Execution History in SAS Customer Intelligence Studio correctly shows Occurrence Number 1, 2, and so on, along with Status Successful.
  4. The CI_COMMUNICATION table correctly shows COMMUNICATION_OCCURRENCE_NO 1, 2, and so on.
  5. Now make the Custom Diagram Tools fail on purpose.
  6. Execute the campaign again. This time, the execution returns an error because the Custom Diagram Tools failed to execute.
  7. The Execution History still shows successful executions.
  8. Correct the error for the Custom Diagram Tools so that the campaign executes successfully again.
  9. Then, execute the communication and not the campaign.
  10. Execute the communication two times. The Execution History in SAS Customer Intelligence Studio is still correct:

image label

When you execute a campaign that fails (for this example, COMMUNICATION_OCCURRENCE_NO 7) and then re-execute the next successful communication (for this example, COMMUNICATION_OCCURRENCE_NO 8), the CI_COMMUNICATION and CI_CELL_PACKAGE tables are incorrect. As shown below, the next successful execution, COMMUNICATION_OCCURRENCE_NO 8, is missing in CI_CELL_PACKAGE and CI_COMMUNICATION tables.

image label

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



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing AutomationMicrosoft® Windows® for x646.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8 Enterprise x646.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8 Pro 32-bit6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8 Pro x646.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8.1 Enterprise x646.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8.1 Pro6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 20086.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2008 R26.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2008 for x646.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2012 Datacenter6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2012 R2 Std6.36.59.4 TS1M19.4 TS1M3
Microsoft Windows Server 2012 Std6.36.59.4 TS1M19.4 TS1M3
Windows 7 Enterprise 32 bit6.36.59.4 TS1M19.4 TS1M3
Windows 7 Enterprise x646.36.59.4 TS1M19.4 TS1M3
Windows 7 Home Premium 32 bit6.36.59.4 TS1M19.4 TS1M3
Windows 7 Home Premium x646.36.59.4 TS1M19.4 TS1M3
Windows 7 Professional 32 bit6.36.59.4 TS1M19.4 TS1M3
Windows 7 Professional x646.36.59.4 TS1M19.4 TS1M3
Windows 7 Ultimate 32 bit6.36.59.4 TS1M19.4 TS1M3
Windows 7 Ultimate x646.36.59.4 TS1M19.4 TS1M3
64-bit Enabled AIX6.36.59.4 TS1M19.4 TS1M3
64-bit Enabled Solaris6.36.59.4 TS1M19.4 TS1M3
HP-UX IPF6.36.59.4 TS1M19.4 TS1M3
Linux for x646.36.59.4 TS1M19.4 TS1M3
Solaris for x646.36.59.4 TS1M19.4 TS1M3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.