Do you have any question about this error?
Message type: E = Error
Message class: WL - Workflow: run-time messages
Message number: 377
Message text: Inconsistent workflow definition: Node/step number & does not exist
When the work item no. &V2& sent a response message, an inconsistency
was found in the related workflow definition: Node no. &V1& has a line
but no node definition or step definition.
The respective workflow task (definition no. &V3&, version &V4&) may
have been changed during the workflow execution in a way which is not
allowed.
INCLUDE NA_WF_ERROR OBJECT DOKU ID TX
Check and correct the workflow definition. You can display the
structure (nodes and lines) of the workflow definition in the workflow
builder via the menu function 'Extras' -> 'Techn. information' ->
'Definition structure' and -> 'Runtime structure'.
<LS>Extras -> Technical information -> Definition structure </>or
<LS>Extras -> Technical information -> Runtime structure</>
It may be possible to correct the error by activating the workflow or
by using the special function <LS>Extras -> </>Special functions ->
Block correction</>.
If the error continues to occur, please check the contents of the
database tables SWD_STEPS and SWD_NODES for the workflow definition
specified above to find out more information about the cause of the
error. You should also send a problem message to SAP containing this
information.
Error message extract from SAP system. Copyright SAP SE.
WL377
- Inconsistent workflow definition: Node/step number & does not exist ?Get instant SAP help. Start your 7-day free trial now.
WL376
Inconsistent workflow definition: Join for fork node no. & not found
What causes this issue? When the fork was entered from node no. &V1&, the respective end in the workflow definition was not found (join node ...
WL375
Fork from node & has not been released again yet
What causes this issue? The fork from node &V1& cannot be entered again yet in workflow no. &V3& since it still contains open activit...
WL378
Task & cannot be started immediately
<ZH>&CAUSE&</> The task &V1& (no. &V2&) cannot be started immediately by user &V4&. Possible reasons: The...
WL379
No agent in '&' is allowed to process task &
What causes this issue? &V1& was specified as <DS:GLOS.3526B11CAFAB52B9E10000009B38F974>responsible agent</> for step &V2&...
Click on this link to search all SAP messages.