You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

How to troubleshoot runtime exception errors in Configuration

Received Response
edited Nov 1, 2022 7:07PM in Configure Price Quote 2 comments


Based on data in the error log, how do you identify the rule that is triggering the runtime exception error?


When I encounter a RuntimeException error, the first place I look for information is the Error Logs (bm.log).  The logs will often provide me with an ID like the example below:

12 Jan 2021 11:50:39,473 [ERROR] - System exception A RuntimeException has occurred.
    at ~[?:?]

My understanding is that "1471537219" is the ID for the rule action causing the error.  Unfortunately, when I download Configuration Rules, the output does NOT include action IDs, only rule IDs.  For example, knowing which rule caused the error, I can find the rule (<id>1471537217</id>) ID in the output but there is no reference to "1471537219".

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!