LAPP is a piece of custom code to achieve a custom requirement which cannot be fulfilled through UI. Many times LAPP fails because of various reason which results halted operations and disturbed dependency of business logic in a CRM account.
Reasons could be:
01. Time-out errors
02. Failed LAPP Logic.
03. In-appropriate error handling.
04. API failure etc.
A support engineer can re-run the LAPP in order to:
01.) Re-produce the issue.
02.) To verify if it was an intermittent error. (In case of time-out errors)
03.) Cross-verify the resolution provided by Development/Engineering Team.
Let’s see how to do it in a step by step manner:
01. Open Postman Tool.
02. Login to LeadSquared account. Find the target LAPP.
A.) You can find it from the automation report where it has been called OR You can directly find it under Apps>Manage LAPP.
02. Click on gearbox icon> Edit. It will take you to the code of the LAPP.
03. Click on ‘API URL: Click to View‘
04. Copy the URL and associated Token of the environment on which LAPP has been published.
05. Go to PostMan:
A.) Paste the LAPP URL with POST method.
B.) Add the Token key (x-api-key) under Headers.
06. Body section can be retrieved from LAPP logs under automation report.
07. Copy the entire data chunk from above step and paste it in Postman window’s body section and hit ‘Send’.
08. You will see the result with success code 200 K.
Points to be Noted:
01. In case of LAPP time-out error Support Eng inner can always evaluate the scenario and increase LAPP time-out accordingly (max 40 seconds) with help of Billing team.
02. Its best practice to try to re-produce LAPP error (if possible) and then report it to Engineering Team accordingly since some of the LAPP errors are intermittent in nature.
