The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Error reporting for workflow operations
Jakub Bochenski
October 12, 2017 edited
One of the most common errors our automation scripts hit is:
08:21:02 { 08:21:02 "errorMessages": [ 08:21:02 "It seems that you have tried to perform a workflow operation (Awesome Transition) that is not valid for the current state of this issue (JRA-1337). The likely cause is that somebody has changed the issue recently, please look at the issue history for details." 08:21:03 ], 08:21:03 "errors": {} 08:21:03 }
Is there anything better one can do to identify this problem other than parsing the error message? This seems brittle. An error code would be much better?
Maybe there is some way to execute the operation as a conditional HTTP request (e.g. If-Unmodified-Since) handling this on another level?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian