When we create an automation that uses the action component "Log output to playbook" we get errors when the automation is triggered outside a playbook. Is there a way to test the source of the trigger and branch to prevent this step if not triggered in a playbook?
hi @Automation
Welcome to the community.
Whenever you ask for help with an Automation Rule it will help us to help you if you provide:
1. what type of project is this (e.g., company-managed, team-managed, etc.),
2. images that show your complete rule.
3. images showing the details of any relevant actions/conditions/branches.
4. images showing the Audit Log details for the rule execution.
5. Explain where the issue is.
These questions are not for not willing to help, but to have community members understand on how automation works.
1. company-managed
2.
3. see above
4.
5. The issue happens when the automation is triggered from the automation button outside of the playbook. This automation can be used in multiple ways. The rule is configured to alert on errors which is triggered when used outside the playbook.
HI @Automation
What are the details of the web hook action and the log action
The webhook sends a few fields to an external product and waits for a response.The log action is a simple set of key-value pairs along with the name of the initiator.
@Automation
Can you show the details of the log action.
Playbook output can't be jst anything, see the related documentation: https://support.atlassian.com/jira-service-management-cloud/docs/run-a-playbook-and-view-outputs/
It looks like you're new here. Sign in or register to get started.
