Automation ID as a smart value

[Myles Boyd]

I am trying to debug an issue when a condition allowing the automation to continue, but the check should fail and the automation stop.

I was hoping to email me the automation ID when this happens so I can investigate easier.

Is there a smart value for it>

Thank you,

[amelia earhart]

I use a primitive debug method that creates some noise but gets the job done: At the end of any automation I make the last step add a comment listing the name and url of the automation that fired.

Like I said, creates noise. However, after debugging, you can delete that noisy comment.

[Marc -Devoteam-]

Hi @Myles Boyd 

Please explain yourself more.

Provide the following:

• What type of project are you using.
• Show your full automation rule
• Show details of each step
• Provide the audit log
• Pinpoint the action where the issue is

Note if you want to find out what a result is, use a log actions.

[Aaron Pavez _ServiceRocket_]

Hi @Myles Boyd 

To better understand this, can you share a screenshot of the automation config you have so far?

Normally, to debug, you'll add a Log action and smart values and then check the Audit log for the automation.

> I was hoping to email me the automation ID when this happens so I can investigate easier.

If you have checked the box to email you when the autoamtion fails, you'll get an email.

Regards

[Myles Boyd]

I do add a log actions, but I was trying to be efficient; instead of scrolling until I find the one that failed, I wanted the automation ID so I could filter on it.

Normally, if an automation fails, you get an email that has the automation ID in.  I wanted to replicate that so I could filter when the conditon is allowing issues through incorrectly.