Workflow: How do I deal with a corrupt definition?

[jensupetersen]

Hello everyone,

we have a workflow sitting in our test system that crashes (causes the transaction to hang indefinitely) whenever you try to do anything with it (i.e. use any transaction on it or one of its instances). This does not only apply to already-existing instances of that workflow: Even if you try to open the workflow in transaction SWDD, it hangs. In addition, this workflow causes memory problems on the system as it appears to consume huge amounts of memory in the process.

Trying to transport a fixed version of that workflow from our development system has not helped. What can we do if we cannot even open the workflow in SWDD? Is there any sort of correction report for workflows or another approach to get rid of it the hard way?

[pokrakam]

I know the question was a while ago, but as this may be relevant in other cases....:

Please also check what is happening when it 'hangs', SM50 is the first place to look. Often it's not the WF, but some code in the business objects defined in the container. SWDD and the likes will try to instantiate all objects, and some bad code/design can cause havoc. (e.g. a header object instantiates it's item objects, which in turn instantiate their header object, which ...).