Workflows stopping due to deadlock on INDX

[Watkins, Philip]

continue. A background task has finished and marked as complete but the next
step in the workflow is not reached. At the time of the problem we can
see(ST22) that there were SQL -913 errors on table INDX on the
Get_task_index call in SAPLRHW0. Unsure of
cause of the deadlocks but we could not restart the workflows that had
frozen as no steps in 'ERROR'.How should we deal with this situation?
 I tried to change the status of the last completed step to Error so that I
could then restart but once an item is complete the function modules do not
allow update to error. We believe the next step was not created because the
workflow id could not be returned from INDX.
 
Has anyone had this problem before and been able to re-start the workflows
 
  Regards
    Phil
 
 
 
***********************************************************************************************
The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only.
 
This email and any response may be monitored by Sony United Kingdom Limited.
(6)
***********************************************************************************************