cancel
Showing results for 
Search instead for 
Did you mean: 

Orphaned Nodes in Workflow Log

Former Member
0 Kudos

We are recently facing this issue in existing workflows. When workflow is supposed to proceed to next step, it is creating orphaned and unknown node types. Sometimes causing short dump DBSQL_DUPLICATE_KEY_ERROR. This error is occurring in multiple workflows randomly/rarely without any pattern. Sometimes this occurs as soon as document is created and workflow triggered and sometimes in middle of in process workflow.

Workflow is processed afterwards as expected by reprocessing job SWWERRE. I have searched SAP community and OSS notes but not found any details on this. Any inputs on this error is much appreciated.

Thanks!

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186746
Active Contributor

Hi,

Use transaction SWU7 and do a consistency check on these workflow templates. Also check OSS for similar issues, there might already be a solution for this behaviour.

Kind regards, Rob Dielemans

pokrakam
Active Contributor
0 Kudos

This almost definitely looks like your WF template is corrupt. This could be due to a failed transport or a number of other reasons. If Rob's suggestion hasn't helped, reactivate from Dev and retransport the whole template.

If that doesn't help, rebuilding a new WF from scratch may be the quickest and most reliable route.