Rule Run Order
Earlier behaviour : Rules / Rule Chain were running in the order they were scheduled and only one rule run per tenant was running and the other are just queued up. So when you had the rules scheduled to run at 12:01, 12:02 and 12:03 this was running in the respective order.
This was causing a huge backlog in the queue and when there were historical runs it was causing several hours delay in rules completion and in some scenarios many days where techops team had to intervene and abort it.
Current behaviour : Rules may run in parallel. We have a cool dependency analysis infra, which will evaluate whether two rules can run in parallel or not by looking at the objects that they are writing into and reading from. This makes sure admin need not analyse and put all the CTA creation rules in a chain or when you are moving the data from Object A --> to Object B --> Object C this will run in the order if was scheduled to run at 12:01, 12:02 and 12:03 in respective order.
This makes sure the rules are executed faster by reducing the wait time in queue and also the manual rule runs have higher priority than any of the scheduled ones. This has enabled us to increase the frequency of the rules in Summer release and will follow with rule chain in Fall release.
What should you do :
If you have some rules that need to run in order at any cost or if you have rule that write to an Object like Contact in salesforce has triggers that impact other objects then Gainsight would not be able to detect the dependency and you need to put the rules in a rule chain to mandate the order.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.