JSM playbooks and automations don't always record in execution log

[matthew barrett]

Playbook automations rules ran from the Playbook Actions submenu in the global automation menu does not register in the playbook execution logs.

I feel like this should be a feature and I shouldn't have to include additional automation rule steps to push logs into the playbook and will probably end up with duplicate entries if I do that and the rule is ran directly from the playbook.

EDIT: After messing with the automation rule that pushes info into the playbook, this appears to only work when the automation is launched directly from the playbook.

Here is an example of what I am talking about:

[Marc -Devoteam-]

Hi @matthew barrett 

It seems that currently this is not recorded, there are 2 open feature requests around this topic, see:

• JSDCLOUD-16802 
• JSDCLOUD-18947 

[matthew barrett]

Thanks!

I see those are similar, but not exactly the same. In my case its flipped -- the actions are recorded in history but not in the playbook execution logs. It's likely all part of the same solution though.