Constraints Deferred to Post Commit: Error Handling

See Also

Problems could occur if an endless loop is created as a result of constraints deferred to Post Commit. Such a problem will be handled the same way as other constraint loops are handled. The 'maximum constraint depth' is checked, and if it is exceeded, the following message will be displayed:

Recursive constraint check exceeds allowed depth of <Parm1> steps.

Following that, an information message will be displayed with a report of how many records were committed in previous transactions, for example:

NOTE:

This type of rollback message is only displayed if a second (or higher) transaction chain fails.