Replies

Avatar

Avatar

HowardTreisman

Avatar

HowardTreisman

HowardTreisman

29-06-2008

You may be able to go into Adminui, and assign the task to a "dummy" user.

Howard

http://wwwa.avoka.com

Avatar

Avatar

Stuart_Mail

Avatar

Stuart_Mail

Stuart_Mail

29-06-2008

Hi Howard

Unfortunatly you can't reassign them as they show as 'Completed' in the AdminUI Task Search so the option is not available.

Stuart

Avatar

14-07-2008

I think the reason you would see such behaviour is because the associated task and action are orphaned. You created your process and then you started it and it got to an Assign Task service and then you decided that you want to modify your process map. Unfortunately to avoid this then you need to modify the database tables manually. The following steps are not recommended and not supported but they will solve the problem:

- Find the process id and query that in tb_process_instance. You will see that the status field for that record is something other than 2. If you change that entry to 2 then this will see the process as complete

- Query the process id in tb_process_action. Look for the process_instance_id field and you will see that at least one of the records does not have 2 for the status field. If you change that entry to 2 then this will see the action as complete.

Avatar

09-11-2008

I have meet this problem too. If you clear the data of tb_task that is a table of adobe database, those info will never appear in the workspace user's "to do" list.

Avatar

Avatar

Jasmin_Charbonn

Avatar

Jasmin_Charbonn

Jasmin_Charbonn

11-11-2008

You can use the adminui interface (http://localhost:8080/adminui) and go under Services/Process Management/Stalled Operations Error to remove them.



This has been there since 7.0. You shouldn't have to go directly to the database to clear those up.



Jasmin

Avatar

Avatar

Stuart_Mail

Avatar

Stuart_Mail

Stuart_Mail

11-11-2008

Hi Jasmin



AdminUI works for stalled tasks assigned to Users but not if assigned to Group Queues. See previous posts form Howard and I on this topic.



As far as I'm aware this is a bug and it still exisisted in SP2 - I have not tried it in U1.



Best Regards - Stuart

Avatar

Avatar

Jasmin_Charbonn

Avatar

Jasmin_Charbonn

Jasmin_Charbonn

11-11-2008

Did you log a bug with support?



Jasmin

Avatar

Avatar

Stuart_Mail

Avatar

Stuart_Mail

Stuart_Mail

11-11-2008

Hi Jasmin



No - from Howard's reply #6/17 "Are you running Service Pack 1b. I'm pretty sure this was a bug that was fixed at some point. The bug still exists if the task is assigned to a group." I assumed that it was already logged.



Best Regards - Stuart

Avatar

Avatar

NW987

Avatar

NW987

NW987

20-11-2009

Has anyone attempted to terminate stalled processes with SP3? 

I 50 some stalled process instances that I cannot terminate.  When I select a large group and attempt to terminate them in a batch, the number of stalled instances will actually increase.

Many of them have an UNKNOWN operation name.  And it actually appears that terminating is actually retrying the operation in many cases.