Failure notifications on Real Time rules

Hi @bradley!

Thank you for the idea! We currently do that for most of our GS to SFDC fields.
However, a few of those fields are bi-directional. So we can’t mass update from GS to SFDC if it doesn’t sync up with our SFDC to GS sync or we are risking overwriting old data back into the field.

I see this is changed to “Discovery” - does that mean it’s actively on the roadmap now?  Do we have a target ETA?

 @anirbandutta may you help us get an update from PM here? Thanks!

Yes… the earlier ‘Under Consideration’ stage is now ‘Discovery’.

@rakesh would be able to share light on this request.

Adding my vote. This is needed yesterday!

Kinda sad this still doesn’t exist.

And that we have to duplicate by creating HREs as a catchall in case the RTR doesn’t catch changes. 

RTR is really pretty unreliable.

@bradley I don’t know Bradley, I think this may be the first time we somewhat disagree on something. 😂 That seems awfully complicated - moreso probably than just a simple notification process (something akin to Connectors posted below).  And the occurrence of multiple failures doesn’t necessarily mean its same issue that caused each failure. 

I do believe admins should have the autonomy to choose real-time notifications for any failure or maybe if they want a “daily digest” as well as the ability to identify the type of failures to notify, but I wouldn’t want the delivery of an MVP solution to hinge upon more granular throttling capabilties.

 

☝ This is an awesome idea, @darkknight -- and now that Slack is baked into dynamic JO, it feels like we should DEFINITELY be able to configure Slack notifications. And notifications within Gainsight.

Notifications where we work is key. 

I get emails when a JO query fails -- but a Slack notification in a shared channel my team has visibility into, for coverage when one of us is out, would be ideal. #parity!

Another thought for failure notifications. I think not just failure notifications but the ability to set a notification for “If no activity in X time period, send notification” would be huge for RTR. Often times we don’t see failures, but we see lack of activity, which hints at a config issue or even a GS bug. While the rule isn’t failing, it is not running, and that is a sign of an issue as well.

Yes! This would make monitoring JOs for failures significantly easier as well -- a lot of programs might not have daily participants, but if a program goes for a couple weeks (or a month) without participants, odds are good something has broken.

Checking if there’s any news about this idea...

We’re beginning to roll out usage of RTRs for tracking updates on existing risk CTAs via a custom object -- having logs and failure notifications for this type of rule to ensure awareness is especially important. It’s a big gap that I hope to see improvements on soon.