Rule chain for Cron Expression schedules
None
Hello Team,
It would be great if we could filter out all the rules that are scheduled for a specific cron expression. For instance say 2 hours.
Also along with filtering could we have a rule chain that brings together the rules based on cron job. This would allow us to ensure they run in a specific order.
Regards,
Jahnavi
It would be great if we could filter out all the rules that are scheduled for a specific cron expression. For instance say 2 hours.
Also along with filtering could we have a rule chain that brings together the rules based on cron job. This would allow us to ensure they run in a specific order.
Regards,
Jahnavi
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.
Although we do not have Rule filtering based on cron expression in the near term roadmap, but it will be good to hear/read if other users also feel that it will be valuable for their use cases.
Regards,
Jitin
Am I taking crazy pills or would this be useful?
Hi@bradley We currently do not have any short term plans around bringing Cron expression for rule chains. Cron expressions allow for one of the 2 things:
While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here.
Hi@bradley We currently do not have any short term plans around bringing Cron expression for rule chains. Cron expressions allow for one of the 2 things:
While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here.
Hi@bradley We currently do not have any short term plans around bringing Cron expression for rule chains. Cron expressions allow for one of the 2 things:
While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here.
Completely agreed with Bradley here. This is a little frustrating, considering Data Designer scheduling now also supports it...consistent user experiences are unheard of across the platform at this point, and we would really like to contribute to solving this problem!
+1 lot of use case if we have this option.
Hi,@rakesh , I agree with @bradley . This functionality should be available soon in next few upgrades.
Cron rule chains helps to manage better hierarchical rules than the edged single rules. Scheduling series of rules are not achieved in regular terms of cron but rule chain aligns it when enabled.
+1K votes.
Please involve techops to get this change worked. Thanks!
+1000 on this one. We have a Rule chain of 7 rules that are required to run sequentially that updates our entire engagment model. We’ve had requests from our global cohorts that a more frequent update of the model (not midday as it is based on US time) would be the most ideal situation.
As noted above, Admins have the ability to schedule rules to fire at custom intervals via CRON. If a rule chain is just a logical grouping of rules, then this should not be of great concern.
If the concern is focused on backend performance taking a hit if all of us started to do this, then that might be another thing to discuss :)
In closing, this was something we “expected” to be part of a consisten Admin interface when “scheduling things in Gainsight” since it is offered elsewhere.
+100000 to this request. The inconsistency regarding using experience across the platform is very frustrating...
To fill this gap we admins have to:
a) Clone chains, if you need to run the same chain more than once, the only way is to clone it and set each one to the required schedule (eg, twice per day every 12 hours).
b) Have separated rules that should be chained, scheduled to run a different times. It’s difficult to see at a glance that they are actually rules that work as a whole (eg, In my instance we have some rules that should run the 8th calendar day of the month in a certain sequence. Instead of having one chain with n rules, I have to manage this sequence via each individual schedule, “0 0 1 8 1/3 ? *”, “0 30 1 8 1/3 ? *”, etc...).