Skip to content

Update troubleshooting.markdown #38941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
May 9, 2025
Merged

Update troubleshooting.markdown #38941

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
921a295
Update troubleshooting.markdown
Didgeridrew May 8, 2025
b60ab1d
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
536cb96
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
84b6eaf
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
847d7c9
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
e7d132e
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
2b70f89
Update source/_docs/automation/troubleshooting.markdown
Didgeridrew May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/_docs/automation/troubleshooting.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ Many automations can be tested directly in the automation editor UI.

### Running the entire automation

In the three dots menu in the automation list or automation editor UI, select the **Run** button. This will execute all of the {% term actions %}, while skipping all {% term triggers %} and {% term conditions %}. This lets you test the full sequence of actions, as if the automation was triggered and all conditions were true. Note that any [trigger ID](/docs/automation/trigger/#trigger-id) used in your triggers will not be active when you test this way. The Trigger ID or any data passed by in the `trigger` data in conditions or actions can't be tested directly this way.
In the three dots menu in the automation list or automation editor UI, select the **Run actions** button. This will execute all of the {% term actions %}, while skipping all {% term triggers %} and {% term conditions %}. This lets you test the full sequence of actions, as if the automation was triggered and all conditions were true. Note that any [trigger ID](/docs/automation/trigger/#trigger-id) used in your triggers will not be active when you test this way. The Trigger ID or any data passed by in the `trigger` data in conditions or actions can't be tested directly this way.

You can also trigger an automation manually. This can test the conditions as if the automation was triggered by an event. Navigate to {% my developer_services title="**Developer tools** > **Actions**" %}. In the **Action** drop-down, select **Automation: Trigger**, then **Choose entity** to select the automation you are testing. Toggle whether to skip the conditions, then **Perform action**. If needed, additional `trigger` or other data can be added in the YAML view for testing. The [trigger](/docs/automation/trigger/) page has more information about data within the trigger.

Testing with complex triggers, conditions, and variables can be difficult. Note that using the **Run** button will skip all triggers and conditions, while **Developer Tools** can be used with or without checking conditions.
Testing with complex triggers, conditions, and variables can be difficult. Note that using the **Run actions** button will skip all triggers and conditions, while **Developer Tools** can be used with or without checking conditions.

### Running individual actions or conditions

Expand Down