Response from Customer

Rule chain for Cron Expression schedules


Userlevel 6
Badge
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

12 replies

Userlevel 5
Hi Jahnavi,

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
Userlevel 7
Badge +2
I would personally love this feature. The previous addition of Bionic Rule chains has been great, but I am currently limited to only run it once a day. My alternative is to have the rules be separate and run every two hours. Unfortunately, they might not catch the items I need them to until a full 4 hours has passed. If I were able to do a Bionic Rule Chain running every two hours, it would cover everything for me. This would also not increase the workload on Gainisght as I am already running the two rules individually every two hours. Adding the option would just make things more efficient.
Userlevel 6
Badge
Any updates here?

I also need this capability. We have customers that get set up hourly so we would like to be able to have them in Gainsight more than once a day. Additionally, CTAs change customer stages and we want that to be reflected more than once a day.

Userlevel 7
Badge

@sai_ram  @ana_g @darkknight @gunjanm   Can you help me revive this thread? I think real-time and event rules are great but they currently only support API calls and SFDC object loads. Can we get cron support for rule chains? Right now the workaround is running each rule individually off of a cron and staggering their run times. But even with this workaround, you don’t get the dependencies that are the backbone of rule chains.

Am I taking crazy pills or would this be useful?

Userlevel 7
Badge +2

@bradleymcg really sorry for the inconvenience. I will try to get a quick reply on this. 

Userlevel 7

Hi @bradleymcg  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:

  1. Flexibility
  2. More frequent runs 

While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here. 

Userlevel 7
Badge

Hi @bradleymcg  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:

  1. Flexibility
  2. More frequent runs 

While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here. 

@rakesh  Thanks for the feedback. Out of curiosity, what is the concern with frequency? As I mentioned, at least for some use cases you can cron schedule a series of rules timed to “run one after another” at a frequency already so how would adding that functionality to rule chains be any different except a vastly improved user experience? You could role it out with guardrails if there’s a concern with processing power for large chains being run more frequently, while still improving the usability of the product.

Userlevel 7
Badge +1

Hi @bradleymcg  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:

  1. Flexibility
  2. More frequent runs 

While providing flexibility is not a challenge per se, we would have to consider a lot of possibilities for providing a higher frequency here. 

@rakesh  Thanks for the feedback. Out of curiosity, what is the concern with frequency? As I mentioned, at least for some use cases you can cron schedule a series of rules timed to “run one after another” at a frequency already so how would adding that functionality to rule chains be any different except a vastly improved user experience? You could role it out with guardrails if there’s a concern with processing power for large chains being run more frequently, while still improving the usability of the product.

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!

Userlevel 3

+1 lot of use case if we have this option.

Userlevel 5
Badge

Hi, @rakesh , I agree with @bradleymcg. 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!

Userlevel 7
Badge +1

+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.

Reply