Symptoms
Processing server/logs report an error similar to the following.
Processing tasks fail and may loop continuously. This will prevent a group of documents progressing through the workflow.
Cause
Loss of a session can leave 'orphan' tasks. This may be due to processing station crash amongst other factors.
Resolution
- Log into Admin & Monitoring console.
- View 'sessions' and identify any related to the batch in question. Remove these sessions.
- Open SQL management studio
- Inspect dbo.Task for any entries corresponding to session ID xxx (235713 in our example screenshot).
SELECT * FROM dbo.Task WHERE EditSessionId = xxx;
Delete any affected rows.DELETE FROM dbo.Task WHERE EditSessionId = xxxx;
- Inspect dbo.SessionTask for any entries corresponding to session ID xxx (235713 in our example screenshot).
SELECT * FROM dbo.SessionTask WHERE SessionId = xxx;
Delete any affected rows.DELETE FROM dbo.SessionTask WHERE SessionId = xxxx;
- Look for any remaining tasks related to the affected batch. First, find the batch ID
SELECT Id, [Name], CreationDate FROM dbo.Batch WHERE [Name] LIKE '%the batch name (or part of it)%';
then remove any related tasksDELETE FROM dbo.Task WHERE BatchId = <result from above>;
- Inspect dbo.Task for any entries corresponding to session ID xxx (235713 in our example screenshot).
If this procedure does not resolve the issue then raise a support ticket.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article