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

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

Change Notice is stuck at 'release changeable'. The resulting objects state is still unchanged

KSHITISH_S
13-Aquamarine

Change Notice is stuck at 'release changeable'. The resulting objects state is still unchanged

A Change notice is stuck at 'release changeable' . The 'Audit Change Notice' is already completed. But the documents in the resulting objects state is not yet changed. The change notice is still running.

 The error in the process manager is attached

Is there a way out?

4 REPLIES 4
avillanueva
22-Sapphire II
(To:KSHITISH_S)

Is this a new system or one that has been running fine for some time? Based on the error, it failed at setting the lifecycle state of some objects in the Resulting Objects table of the change task. See if you can identify any ones that are out of the ordinary. If this is a new system, I would look for a configuration issue with preferences or setup of the lifecycles. You could also try re-executing the failed expression robot. There should be a failed task in the WfUserWorkQueue queue. Are you system admin? If that task errors again, I would look for the object and see if the "release" state is defined properly on them.

cying
12-Amethyst
(To:KSHITISH_S)

If you can share the screenshot of the routing/process that would be helpful.  Typically, when this happens for us is when the objects being routed have been uploaded but not checked in AKA private check-out.  The system is not able to set the previous object to "superseded" thereby it's stuck in the process. 

 

KSHITISH_S
13-Aquamarine
(To:cying)

I have attached the screen shot of the process routing.

avillanueva
22-Sapphire II
(To:KSHITISH_S)

If you select on that step, in the bottom panel should be a snipit of the error message which caused it to fail. Can you see if you see that? Also did you check the failed job in the QueueManager?

Announcements


Top Tags