Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# 1810

Sub-case not started due to reaching nesting limit of NestingLimit in ProcName-CaseNum-StepName.

Description

A Background process (BG) failed to start a case of a sub-procedure because the system’s maximum sub-procedure nesting depth has been reached.

Appears In

SWDIR\logs\sw_warn

Severity

2 (Severe)

Action

To resolve this problem, do one of the following:

| • | Check the specified ProcName and StepName to see if there is a problem in the procedure logic. For example, a sub-procedure that calls itself, a group of procedures that call each other in a loop, or a condition in which the exit criteria are not being met, thus creating an infinite loop.

or

| • | If this is not the case, use the SWDIR\util\swadm command to increase the value of the MAX_SUB_PROCEDURE_DEPTH process attribute, which defines the system’s maximum sub-procedure nesting depth.

See Also

“Administering Process Attributes”, in TIBCO iProcess Engine Administrator's Guide, for more information about the SWDIR\util\swadm command.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.