Issue Summary

If there are two active workflows configured for SLAs against the Incident Table, SLA Tasks may get start and end timestamps set instantly within one second each other. The workflow is not waiting for the SLA timer.


Solution Proposed

This behaviour is due to running SLAs asynchronously. Setting the system property 'com.snc.sla.engine.async' to false should resolve the issue.


Article Information

Last Updated:2018-06-11 16:30:38