Few leads are not being scored using Einstein Discovery due to locking contentions.
Last updated 2022-02-10 ·Reference W-7715295 ·Reported By 0 users
Summary
When Leads are loaded in bulk using any api, We see few of these leads are not being scored by Einstein Discovery. These failure are happening due to row lock contentions on the lead records.
Actual Results:
When leads are created few of these leads are not scored by Einstein Discovery
Expected Results:
When leads are created all these leads should be scored by Einstein Discovery
Repro
When org have set up to lead scoring using Einstein discovery, Load leads in bulk to the org and see few leads are missing the scores.
Workaround
N/A
Reported By (0)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.