Groovy Script Trigger on Leads Performance Error 400 Bad Request oracle.jbo.script.ExprTimeoutException Expression timed out
(Doc ID 2826656.1)
Last updated on OCTOBER 13, 2023
Applies to:
Oracle Fusion CX Sales Cloud Service - Version 11.13.21.07.0 and laterInformation in this document applies to any platform.
Symptoms
User getting 400 Bad Request when calling REST api to create a lead. If try again with the same payload, then it create it successfully. This is also happening in the UI when creating a lead.
Payload
POST https://XXXX.fa.em3.oraclecloud.com/crmRestApi/resources/latest/leads
{
"PrimaryContactId": "300000040288500",
"OwnerId": "300000008091025",
"Showroom_Id_c": "300000009122038",
"Requester_Emp_No_c": "03605944",
"Requester_Emp_Name_c": "Test Rep1",
"Brand_c": "CHERY",
"Model_c": "TIGGO7 PRO",
"ChannelType": "REFERRAL"
}
Response
HTTP/1.1 400 Bad Request
Location: https://XXXX.fa.em3.oraclecloud.com:443/crmRestApi/resources/11.13.18.05/leads/300000040288629
Exception in expression "oracle.apps.marketing.leadMgmt.leads.model.entity.MklLeadEO.CustomerID_c": oracle.jbo.script.ExprTimeoutException Expression timed out.
at "oracle.apps.marketing.leadMgmt.leads.model.entity.MklLeadEO.CustomerID_c" expression line 1
at "oracle.apps.marketing.leadMgmt.leads.model.entity.MklLeadEO" trigger "LeadAge" line 15
Changes
BeforeInsert object trigger "LeadAge" created on Sales Lead in Application Composer
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |