Skip to main content
The past two days we have experienced 2 and 3 hour delays with Outreach schedule.  This causes our Outreaches to run into downstream related Rules that are based on email logs.  Two suggestions:

1.) It would be great if the Gainsight status page could be updated if an queues are delayed more than 1 hour.

2.) It also would be great if we could manually pause all Gainsight Rules.  This way we could wait for all emails to be sent.  Note that there is already another post to allow for dependent scheduling between Outreaches and Rules.
Thanks Jeffrey, great idea. Do you have the link to that other post? I would like to up vote that one as well. Its a pretty major part of our renewal notification automation and connecting Outreaches and Rules could save us some occasional headaches.
Here is the post that referred to having a common scheduling queue across Outreaches and Rules: https://community.gainsight.com/gainsight/topics/trigger-copilot-email-via-rule
Jeff - Thanks for bringing this up. 

I'm putting down our thought here which will get implemented in next couple of releases


  1. Option to trigger a rule / rule chain after a data load is complete
  2. Enhancing the above option, trigger an outreach after a rule chain process is completed.
Apart from the above, better management of these scheduled jobs across gainsight is part of our thought process.



Hope this direction will help you in better managing the rules and outreaches.
Sundar - Not sure what you mean by a "data load".  We would like the ability to trigger a rule / rule chain after an Outreach chain. #2 would be helpful too so that we can trigger a Outreach chain after a rule chain.



Background: We have many Rules that need to be run before our Outreaches get sent.  Then we have wait for these Outreaches to complete before run another set of rules.



Note: If "data load" is referring tot he S3 ingest jobs then yes we would love to set up dependencies with these as well but not as important as what is mentioned above because we never have issues with ingest jobs and they run super quick.
Yes I meant Ingest jobs.

Thanks for the background,  yes #2 would be extended further to trigger outreach after rules and vice versa. 
We are primarily interested in the ability to pause certain actions for maintenance.  In our specific case it's the load to SFDC actions that need to be paused during a large data push from another system.  Pause all would work fine for us in this case.  However, the ability to pause actions by action type would further enhance this capability.  ex: pause all "load to SFDC object" actions.
Hi All, Pause and Resume capabilities in Rule Schedule is available in October release. 



Please refer the release notes for more information. 



Thanks for bring this up!

Reply


Terms & ConditionsCookie settings