Transport leads to "Inconsistent workflow definition"

[Mark Pyc]

G'day Wugers,

Version 6.20 patch 41.

I'm also raising this with OSS, but I'm open to any suggestions.

I have a Workflow which is working in Dev but when transported to QA
is giving me grief. Initially when the transports went in the first
subflow to be called (either a 1 or 2 stage approval subflow) would
fail with message "Inconsistent workflow definition: Node/step number
1 is not available". The long text of error WL377 says to look at the
runtime structure and try Block Correction and to look at the contents
of tables SWD_STEPS and SWD_NODES. Without really knowing what I'm
expecting to see in these tables this gives me no joy (block
correction says 'No Probs').

I tried a simple reimport of the transports which resulted in the main
Workflow suffering exactly the same issue "Inconsistent workflow
definition: Node/step number 1 is not available".

I next tried generating a new version of each Main and Subflow in Dev
and retransporting. This had the effect of fixing the main flow, but
again the subflows now fail with the same message.

This indicates to me that I'm facing a transport issue. The note
686297 (already mentioned today) has been applied.

The long text of WL377 also says to raise an OSS message - so that's
just what I'll do.

Any takers?

Have fun,
Mark

(what did I say about needing to allow for OSS note application in
Development quotes???)