Problem Note 55326: Re-executing a communication in SAS® Customer Intelligence after a failed execution does not update the COMMUNICATION_OCCURRENCE_NO table correctly
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:
- Create a simple campaign by selecting Select Node ► Cell Node ► Communication Node ► Custom Diagram Tools.
- Execute the campaign.
- The Execution History in SAS Customer Intelligence Studio correctly shows Occurrence Number 1, 2, and so on, along with Status Successful.
- The CI_COMMUNICATION table correctly shows COMMUNICATION_OCCURRENCE_NO 1, 2, and so on.
- Now make the Custom Diagram Tools fail on purpose.
- Execute the campaign again. This time, the execution returns an error because the Custom Diagram Tools failed to execute.
- The Execution History still shows successful executions.
- Correct the error for the Custom Diagram Tools so that the campaign executes successfully again.
- Then, execute the communication and not the campaign.
- Execute the communication two times. The Execution History in SAS Customer Intelligence Studio is still correct:
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.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8 Pro 32-bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8 Pro x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2008 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2008 R2 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2008 for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Datacenter | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Std | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Microsoft Windows Server 2012 Std | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Enterprise 32 bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Home Premium 32 bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Home Premium x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Professional 32 bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Professional x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Ultimate 32 bit | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Windows 7 Ultimate x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
64-bit Enabled AIX | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
64-bit Enabled Solaris | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
HP-UX IPF | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Linux for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.4 TS1M3 |
Solaris for x64 | 6.3 | 6.5 | 9.4 TS1M1 | 9.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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2015-03-24 13:47:40 |
Date Created: | 2015-03-05 11:28:08 |