Deferring conditional event checking

Actual as of v2.8.7.

Within a period defined by the config parameter bpmnPendingDeferPeriod ("6 hours" by default) pending conditional events nodes are being checked as soon as possible. After that period they will be checked with an interval defined by the parameter bpmnPendingDeferIntervalPeriod ("10 minutes" by default). This is an optimization measure.

If the entity is updated, it will make nodes related to that entity to be checked one time regardless whether the defer period is passed.

Pending event checking limit

The config parameter bpmnProceedPendingMaxSize (20000 by default) limits max number of pending flows that can be processed. Consider increasing it if you usually have a large number of acrive processes.

Multi-instance sub-process limit

The max number of sub-process instances (within a multi-instance sub-process) is defined by the config parameter bpmnSubProcessInstanceMaxCount. The default value is 20.

Try AutomaticERP for free

Automated system for company management

Do you want to receive news from the world of corporate systems, technical news and data? Send us your email and we will send you a newsletter.

Demo AutoCRM

Our team of consultants will guide you through the process of deploying AutoCRM in your company.