Do you have any question about this error?
Message type: E = Error
Message class: WL - Workflow: run-time messages
Message number: 392
Message text: Maximum node number reached in process execution (endless loop?)
At present, a maximum of &V3& nodes are allowed in one workflow - see
settings for workflow runtime system or basic data of the workflow
definition. During execution of the confirmation for work item &V1&,
the node counter was increased to value &V2& while step number &V4& was
being processed.
The workflow was stopped as a precaution.
Please check the various steps of the workflow in the workflow log:
If an endless loop is actually occurring, please correct the workflow
definition accordingly.
In order to continue the current process, execute the option <LS>Edit
-> Set upper limit</> in the report program <DS:TRAN.SWPR>Restart
workflow</>.
If the configured <LS>maximum node number</> for this workflow is too
small, you should increase the maximum node number for this workflow
definition in the basic data in the Workflow Builder for the following
new workflow instances.
Error message extract from SAP system. Copyright SAP SE.
WL392
- Maximum node number reached in process execution (endless loop?) ?Get instant SAP help. Start your 7-day free trial now.
WL391
Inconsistent workflow definition: Unknown ref. point '&' for deadline
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WL390
Expression '&' does not contain a date or time or has errors
What causes this issue? The expression '&V1&' was specified as a reference point for the deadline calculation for activity no. &...
WL393
Response from work item &: Error writing to database table '&'
What causes this issue? The response message from work item &V1& was processed correctly. However, this fact could not be stored in the datab...
WL394
Workflow no. &: An error occurred in work item & (step no. &)
What causes this issue? An error occurred in the work item in the workflow specified above. The error class, that is the ABAP message type was '...
Click on this link to search all SAP messages.