Clarity

Hi guys, 

we have a problem with process which was working correctly in clarity 12.1.1 but now after release upgrade to Clarity 13.3 we are facing issue. After few seconds when process is active it is automatically set on-hold. 

Heres is an error message from process validation subpage:

The process definition has been put on hold because the number of instances created exceeds the defined limit. Ensure that the start condition of the process is correct and will not allow runaway instance creation.

Does anybody have a clue how can be set the limit of created instances? If there is chance to do so... 

Many thanks, 

Peter B.

Have you checked with support ?

A process storm is detected and the process definition is put on hold even though there is only one process instance per object instance.

There is a bug -

CLRT-74393 - bpmMonitorStormDetector results in false positives when a large number of new object instances each fire one process

Workaround -

Raise the process storm monitor threshold from 100 to something larger than the number of object instances being xogged in (setting in CSA)
or
Disable the storm detector via the properties.xml with : disable="true"

NJ

Hi NJ, 

Great! thanks a lot. After disable it is ok. 

Regards, 

Peter