Ability for Rules to run more frequently than once a day

Any update on this? I have a few rules that I need to run many times in a day (about 10) and right now I'm having to create multiple rules to accomplish this. This becomes very time consuming when making a change to the rule (has to be done for every clone).

I also need this feature and am interested in the progress on it.

We would love this feature! Hourly would be good enough for us as well. Please provide an update when possible. 

Need this feature. We need this run hourly. Is there an update on this?

If you can't change all rules to run real time or periodically like hourly for commercial reasons, what about being able to select frequency for rules... every hour, every 3 hours etc...  That way if I need to modify a rule I could do it once.  Default could be every 24 hours.

This sounds like something that would benefit most customers.  Can this be fasttracked onto the roadmap?

We are working towards it in multi-step. First step would be rule chains and then parallel run of rules and as final step we would enable increasing the frequency of the rules.

Some background on this:
As you know all the rules (for each customer) would run in a sequence defined by the scheduled time. This is essential and it causes the total time taken to complete all the rules anywhere from 1-8 hours. The long running rules for most customers is influenced by the SFDC API response time majorly among other reasons, and thats not within Gainsight's control. By increasing the frequency of rules this will increase to unmanageable levels.

Why doesn't the rules run in parallel now? 
We can't have the rules read / write into the same object and if we have to support then heavy instrumentation should be done in Gainsight's platform which is the second enhancement I mentioned above. 

The long term would look like this

1. Organize the rules that needs to run in a sequence with dependency within a rule chain
2. Rule chains and other custom rules would run in parallel with inbuilt protection (No read/write on same object simultaneously)
3. Rules can be scheduled to run at a lower frequency. 

Our situation:

1. We have cloned the rule that pushes new customers after closed won status occurs for that customer
2. We have closed the rule that creates an onboarding CTA for the new customer

Problem: if that CTA is closed within that same day, the cloned CTA rule will be re-run and applied again so that the same CTA will appear for that customer.

Will date/time functions solve this issue where:
CTA:Created Date >= Subtract 1 Day from Rule Date ?

or do we also have to include CTA:Created date < Add 1 Day from Rule Date ?

Hi Sundar,
Is there an update on this?  We have a need to run an alert rule to run once an hour to meet SLA expectations.

Thanks,
Leslie Morgan

Hi Sundar,

I understand that technical challenges and limitations exist.  At the same time from my experience with other rules engines (Example: Blazes Advisor or others), my expectations are so high.  Love Gainsight, but...