In SAS Customer Intelligence Studio, you might encounter performance issues similar to the following:

• Adding/deleting a node to the diagram or removing/adding the arrows between the nodes might take more than a minute for each action.
• Saving a campaign might take 10 minutes or more.
• Opening a campaign might take 20 minutes or more.

When these issues occur, the following messages are repeated numerous times in the SASCustIntelCore6.x.log file when you set logging tracing level to HIGH:

[aca2e89349f2062c:3f7a116d:150259f444f:3c64] [sasdemo] sas.analytics.crm.flow.ejb.FlowProxyImpl - getDiagramModel: Time taken to 
getDiagramModel: StopWatch '': running time (millis) = 280026
2015-10-02 11:17:01,024 DEBUG [CIAsyncExec-3] [xxx2e89349x2062c:3xxa116x:150259f444f:3c64] [sasdemo] sas.analytics.crm.flow.ejb.FlowProxyImpl - getDiagramModel: Time taken to
getDiagramModel: StopWatch '': running time (millis) = 228581
2015-10-02 11:20:59,404 DEBUG [CIAsyncExec-3] [xxx2e89349x2062c:3xxa116x:150259f444f:3c64] [sasdemo] sas.analytics.crm.flow.ejb.FlowProxyImpl - getDiagramModel: Time taken to
getDiagramModel: StopWatch '': running time (millis) = 211767 
2015-10-02 11:23:13,352 DEBUG [CIAsyncExec-3] [xxx2e89349x2062c:3xxa116x:150259f444f:3c64] [sasdemo] sas.analytics.crm.flow.ejb.FlowProxyImpl - getDiagramModel: Time taken 
getDiagramModel: StopWatch '': running time (millis) = 106018

Note: If you convert the highlighted number above (280026 milliseconds) to minutes, you have a running time of 4.67 minutes.

Communication nodes perform certain validations when they are in a ready for execution state, which can cause the performance delay that is described above. To circumvent this problem, add a Cell node to the diagram and link this node to all of the Communication nodes. When you do this, the Communication nodes are in a not ready for execution state, as shown below:

When the Communication nodes are in this state, there is no excessive performance delay.

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

Operating System and Release Information

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

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