Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow error log

JiraYo
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2020 edited

Hey i have a workflow i am trying to troubleshoot. Its a bit of a hacky funny one, but the specifics aside, i try and submit from portal and get this message:

image.png

 

Just wondering where the actual error is logged to so i can take a look at try and diagnose. All fields are filled out so the error is erroneous as written. I believe it is having trouble sending an email with a plugin because if i remove that line it does work, but i need to see the actual error. Must be logged somewhere right?

1 answer

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2020

Have a look at the application log.  In this case, the error message won't be what you see on-screen, but it should be clear.  Best option though is to look at the time it happened.

Look for <jira home>/logs/atlassian-jira.log - that's where 99% of this sort of error will be logged (expect java detail though, it could be very long)

JiraYo
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 8, 2020

Thanks. i was hoping there was a graphical front end like that way that there is for the automation log, but i was able to find it at the following location.

 

"c:\Program Files\Atlassian\Application Data\JIRA\log\atlassian-jira.log"

 

The problem was that i hadn't made my user that was sending the email (SYSTEM) an administrator on the site. So it couldn't view the resulting issue. The error was "Issue with key 'HOC-18' either does not exist or you do not have permission to view it." But that is very specific to what i am doing. it works now. thanks as always nic.

Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer