Errors on stopping progress

We've just made some changes to our workflow, and since we have we have started to hit spurious/occasional errors from JIRA, but I can't seem to figure out what is going on.

When an issue goes through the sequence (starting from Closed): Reopen -> Start Progress -> Stop Progress

A Workflow Error dialog is displayed that says:

{noformat}Error marking step #56662 finished: root cause: Tried to update an entity that does not exist.

It seems that you have tried to perform an illegal workflow operation.

If you think this message is wrong, please contact your JIRA administrators.{noformat}

After the dialog, the issue reverts (properly) to the Open state, and the dialog doesn't show up again as you start/stop progress repeatedly on the issue; _until_ you restart at Closed.

It seems like anytime the issue starts at the Reopened state, and if you use Start Progress to transition the issue from Reopened => In Progress, the Stop Progress action immediately after that triggers the dialog.

I've looked through the transitions and I can't figure out what I've done wrong.

Could someone have a quick look and let me know what I've done wrong?

Thanks,

Remi

3 answers

I have also run into this issue running version 5.1 of JIRA

The error from the log file is as follows:

com.opensymphony.workflow.StoreException: Error marking step #78204 finished: root cause: Tried to update an entity that does not exist.

Surely someone else see this issue?

0 votes
Joe Wai Tye Atlassian Team Nov 12, 2012

Hi,

Could you try running the Integrity Checker : https://confluence.atlassian.com/display/JIRA051/Using+the+Database+Integrity+Checker. It will check if there are any integrity issues in your database. Sometimes, workflow issues are known to be caused by database integrity.

Cheers,

Joe

Nope checked integrity and no issues found.

Imported 1/2 dozen workflows, all others are fine however this one triggers the error then transitions anyway.

Going to review the source again to ensure I haven't missed anything configured on that staging instance.

We are currently encountering the same issue in a workflow on Jira 5.1.2

The workflow has a design that takes the ticket by default 4 times through "Work Started on Issue" and "Work Stopped on Issue" state changes and the message always comes in the 3rd cycle (either during start or stop action).

I cannot find an issue with the setup of the workflow as it is really plain (even though it involves a total of 27 different status.

Integrity Check did not resolve the issue.

Any idea?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,153 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you