Diagnosing nCino Auto Booking with FIS IBS Code Connect Problems With Glyue Run Histories
This document’s intended use is to allow you to diagnose and solve potential nCino issues on the fly.
A prerequisite for using this document is that you have access to Glyue and to the flow chart provided to you before production go-live. If you do not have access to Glyue or are missing the flow chart, please create a ticket on the Glyue Help Center for assistance.
When Should I Use This Page?
When you’ve attempted to book a loan through the automated booking tab and received an error message like this:
FAILED TO BOOK THE LOAN WITH THE SALESFORCE RECORD ID {Salesforce Record ID} TO THE CORE: [IBSDLB/V1]: {Error Message}
When you see a message like this and do not know why this issue occurred
When you see a message like this and don’t know where the field is in nCino that Sandbox Banking is using to map with
Already Know Where To Go?
Search through Sandbox Banking’s repository of Error Resolution pages to find a potential solution to your problem:
Note: If you don’t see one that matches then please open a ticket through your Glyue Help Center.
- 1 Step 1 – Log Into Glyue
- 2 Step 2 – Navigate to the “Run History” Tab
- 3 Step 3 – Find the Most Recent Run History for the Loan in Question
- 4 Step 4 – Select the Run History to Get More Information About the Booking
- 5 Step 5 – Find the REQUEST Step(s) That Has the Red [!] Next to the Request
- 6 Step 6 – Retrieve Error Message and Potential Cause from the REQUEST
- 7 Step 7 – Find Where the Field is in nCino that Sandbox Banking is Mapping
- 8 Step 8 - Find the Error Resolution Page For Your Error
Not Sure Where To Go First?
Step 1 – Log Into Glyue
Step 2 – Navigate to the “Run History” Tab
Step 3 – Find the Most Recent Run History for the Loan in Question
If you just booked the loan, this should be the first run history at the top of the scroll bar
If you are diagnosing an issue with a loan that was booked at an earlier time, please use the Text Search option on the right-hand side to search for the loan id in question.
The loan id (usually the field id or Record Id in nCino) is also present after
LLC_BI__Loan__c/
in the loan’s URL in nCino, as seen in the example below:If you can’t find the Text Search option, please create a support ticket
Please note that most integration runs that have issues will have a red [!] next to the integration name
If the details section of the Automated Booking Summary page in nCino has a message that says BOOKING FAILED -- RUN TIME ERROR ENCOUNTERED -- PLEASE REVIEW RUN HISTORY this means the loan booking failed due to a runtime error.
Sandbox Banking does not expect you to resolve runtime errors yourself. However, providing as much information to your engineer when opening a ticket is the best way to get the issue resolved quickly.
Runtime Errors manifest themselves in the Stack Trace of a run and may be accompanied by an empty Failure step in the run history. Follow Step 6 to retrieve the Stack Trace and place it in your request through the Glyue Help Center.
Step 4 – Select the Run History to Get More Information About the Booking
The integration name for the run that failed will be the wording next to the red [!] in the runs list
For example, in the image above, the integration name that failed was dlb_ncino_create_ibs_loan
Take note of the integration name for use in Step 7
Step 5 – Find the REQUEST Step(s) That Has the Red [!] Next to the Request
Click on the REQUEST step(s) to open the Details page
Errors will be in the Response section on the Details