Objective: The main objective of this document is to get help in debugging of recurring production issues without the intervention of developer.
Scope: This document covers way to debug the issues.
Note: Please review the LAPP logs thoroughly for any type of issue & for sharing request response to client.
Issue: CAS ID is not generated
LAPP: Data Push to Finnone
Note: First check if we are getting error from Finnone side or LSQ side by seeing logs. We are logging finnone response.
If the issue is from finnone side you can directly ask client to check with Nucleus team & share request response to them which you can easily get from logs.
Possible Errors which you can see in LAPP response in this case:
• Validation errors (Like Only Alphabets, Numbers and spaces are allowed) – These types of errors generally come from Finnone end. So, you just need to ask the client to check this with Finnone team that for which field this error is coming from.
• {applicationId:””,applicationNumber:””} – Check status code coming from Finnone side, if its therein LAPP code or not. If not, then ask for the updated status code list.
• There is an issue with one of the data types. Kindly contact Finnone support – In this case, you must share request response of Application creation Finnone API. We are already logging these, so you just need to pick from LAPP logs. LAPP Log Tags:
- option to application creation
- created application response.
• Source Account Number is mandatory. #Fund Transfer Number is mandatory – As Error is legit, as source account number is getting passed as null from our end.
Schema from which we are fetching source account number is : mx_Custom_80 (mx_CustomObject_15)
•504 Gateway Timeout – This Error is from Finnone API due to their server issue. Please connect with them regarding this.
•IdentificationNumber is mandatory – We get this error from Finnone API. This error usually comes when there is issue with Proof of identification being sent to their API. It can be for any of applicant, so just cross verify at LSQ end what is being sent to Finnone in proof of identification.
•CAS ID is overwritten – Whenever you encounter duplicate CAS ID issue. Just share request and response from LAPP logs with client and ask client to connect with Nucleus team to check for RCA.
• In these cases, kindly check Karza Response in Lapp: Pan Validation – Clean Approach for clarity. And refer below Karza Status codes for specific meaning
• Pin Code is Empty – Check at activity level only, that which Pin code field is being sent as null to LAPP.
