Hi all,Sorry if this is a duplicate question, but I couldn't find anything in the community when searching.
I have a process that has stopped on a user input task. In the process details I can see that the Task Owner is set to the appropriate user, but on the assignment for that specific node I see "Task currently assigned to: " with no value for the assignee.
Attempting to reassign the user input task give me the failure message of, "One or more of the tasks could not be reassigned because the task is cancelled, completed, aborted or is unattended."
I'm guessing you can't REassign something that doesn't have a current assignee.
I'm hoping that there is a way to fix this particular process instance using the Edit Process View, but am not sure how that should be done.
Can anyone please help me figure out how to set the assignee so the task can be completed?
Thanks in advance!
Discussion posts and replies are publicly visible
It sounds like there might be some deeper issue with your process instance - like an actual underlying error either with the task or with the process instance. Could you post a screenshot of what you see when you right-click the task and click "instances"?
Sure thing..
How about if you click the "modify" dropdown in the Process Instance window frame? Are "Pause" and "Cancel" un-greyed-out?
Resume Process is greyed out, but everything else is available. I should add that this process has run successfully hundreds of times before this problem
Everything looks ok so far - other than the stuff I mentioned I'm out of ideas for the moment. Perhaps launch a new instance of the task and see if you can assign that? Otherwise I'd suggest checking the tomcat STDOUT logs to see whether it provides any more specific error messages, etc.
Great! I started a new instance and the correct user is now set as the assignee.
Thank you very much for taking the time to help me
No prob - thanks for confirming, and sorry I couldn't provide anything more concrete. I've found very rarely, like this, something will glitch out with an instance which isn't easily explained by anything we can see on the development side. But luckily I've found this is pretty rare.