CRJAZ6055E/Stale Data
Hi all, very rarely we receive the following in Work items:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.messages.CLMic/CRJAZ6055E.html
The operation cannot be run because the repository contains a newer version of the item it tried to modify. Refresh from the repository and try the operation again. For more details, open the help system and search for CRJAZ6055E.
We try to manually refresh the work items in question, but it seems to be something that is resolved on its own in the backend (sometimes after 1-2 days, sometimes a week).
Do you know if there's a way to manually sync these work items in question? Thanks for any help!
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.messages.CLMic/CRJAZ6055E.html
The operation cannot be run because the repository contains a newer version of the item it tried to modify. Refresh from the repository and try the operation again. For more details, open the help system and search for CRJAZ6055E.
We try to manually refresh the work items in question, but it seems to be something that is resolved on its own in the backend (sometimes after 1-2 days, sometimes a week).
Do you know if there's a way to manually sync these work items in question? Thanks for any help!
One answer
Mark,
I have seen stale data only when I created automation/extensions in the case that the data of the work item I tried to modify was modified in the meantime. In this case you have to refresh the work item before doing the change and refreshing. I am not sure if that could be the case for you as well. It would be good to understand better, when that happens (and in which version). I don't think you can run an operation to fix this, because this should only ever happen if you have conflicting changes on one work item.
I have seen stale data only when I created automation/extensions in the case that the data of the work item I tried to modify was modified in the meantime. In this case you have to refresh the work item before doing the change and refreshing. I am not sure if that could be the case for you as well. It would be good to understand better, when that happens (and in which version). I don't think you can run an operation to fix this, because this should only ever happen if you have conflicting changes on one work item.
Comments
this has been reported before..
https://jazz.net/forum/questions/114354/manually-synchronize-stale-data
I have experienced it multiple times.
restarting the ccm server has been the only way to resolve it.
Thanks Ralph/Sam. We're on 4.0.3 and havent noticed a pattern yet (happens rarely). Refreshing didn't resolve. Going by Sam's note we would need to restart to resolve. (likely won't be able to for 1 impacted work item however) Thanks!