Rule Execution Logs from Scheduled runs not containing Action Details

THis is so frustrating.... It's hard to analyze and troubleshoot rules. I've been wanting to post about this for a while now!... So THANKS Jeff!! 😃

Could not agree more Faust!

FYI, I reported this back in March and I was told it was added as a bug. Hopefully it will be fixed soon enough.

Hopefully VERY soon because I'm afraid I'm going to have to break apart all my rule chains and schedule these rules one by one.

+1 on this.  Been wanting this for a long time. Makes it impossible in many cases to understand why a scheduled rule within a Rule Chain might have failed without manually rerunning the rule (which may not even produce the same error depending on the nature of the issue -- i.e. a timeout).

Agree across the board!

Hi everyone,

Sorry to hear this is paining you! I'm checking with our Support team to see if this is being fixed soon or if it's a new issue.

Thanks for checking into this Lila.  It's a HUGE pain point.

So it appears that this is the case regardless of if it's in a rule chain or scheduled singularly, and it's by design (I haven't run a singularly scheduled rule in a long time, so didn't recall this to be the case)

Can this get converted to an Idea and placed high up on the priority list?  I feel it very important to include these details EVERY time a rule runs because just because it ran successfully doesn't necessarily mean there wasn't a mistake.  Sometimes you need to go back and find out what a rule did days or weeks later when you find a discrepancy.  WIthout this level of detail it's hard to trace things backward.

Hi Jeff,

I heard back from Support and they confirmed that things are working as expected, so I will convert this to an Idea.

"The behavior is that for scheduled executions, we won't send the details of rule actions or successful record counts. So the breakup of per action count will not be shown. In case of a partial success, we will show the number of records which failed though."