Rule Execution Logs from Scheduled runs not containing Action Details

  • 7
  • Idea
  • Updated 3 weeks ago
When a rule chain scheduled rule runs, the execution log does not contain the Action results the way a manual run does.

Scheduled:



Manual: 
 

Worse still, the email that comes through doesn't even tell me the number of records from the Action the way a manual rule does:

Scheduled:


Manual:


This increases the level of effort required to monitor/troubleshoot.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,252 Points 20k badge 2x thumb
  • disheartened

Posted 1 month ago

  • 7
Photo of Faust Belarmino

Faust Belarmino, Champion

  • 1,668 Points 1k badge 2x thumb
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!! :D
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,180 Points 20k badge 2x thumb
Could not agree more Faust!
Photo of Marcelo

Marcelo, Champion

  • 2,882 Points 2k badge 2x thumb
FYI, I reported this back in March and I was told it was added as a bug. Hopefully it will be fixed soon enough.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,180 Points 20k badge 2x thumb
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.
Photo of Rob Begley

Rob Begley, Official Rep

  • 1,296 Points 1k badge 2x thumb
+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).
Photo of Cameron Wright

Cameron Wright, Employee

  • 2,640 Points 2k badge 2x thumb
Agree across the board!
Photo of Lila Meyer

Lila Meyer, Official Rep

  • 15,392 Points 10k badge 2x thumb
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.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,212 Points 20k badge 2x thumb
Thanks for checking into this Lila.  It's a HUGE pain point.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,252 Points 20k badge 2x thumb
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.
Photo of Lila Meyer

Lila Meyer, Official Rep

  • 15,392 Points 10k badge 2x thumb
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."
Photo of Jitin Mehndiratta

Jitin Mehndiratta, Product Manager

  • 2,964 Points 2k badge 2x thumb
Hi Jeff,

When you click on a Rule and go to "Execution History". It shows the execution logs for each execution of that rule.
Does that not help?

Regards,
Jitin
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,252 Points 20k badge 2x thumb
Hi Jitin - no it doesn't because the execution logs do not show the results of the ACTIONS in the rule.
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 24,252 Points 20k badge 2x thumb
How high can we move this up on the priority list?  Without this capability it makes it very hard to troubleshoot when a rule "succeeds" but didn't process the actions as expected.