Hi Everyone,
I am running into a issue that I don't know where to start to diagnose. At our organization we utilize both Kindsight iWave Automatic scoring to score any opportunity that comes into our instance that is over $100 and 999 days since their last scoring or if they haven't been scored at all.
GoFundMePro is our payment portal for users to make donations and sync right into our Salesforce instance. The main issue we are facing is that the managed flow or package that triggers the scoring would fail when GoFundMePro related gifts gets synced in.
Is there any solution or workaround so I can continue have this automation work in order?
#NPSP #Salesforce Developer #Salesforce Admin #Nonprofit
This typically occurs because the automated scoring package or managed flow tries to execute synchronously on newly inserted Opportunity or Contact records simultaneously with the GoFundMePro data sync. When high-volume or third-party payment integrations push records into your instance, the sudden influx of DML operations can cause lock contention or trigger depth limits, causing the scoring flow or trigger to fail before it can evaluate the $100 and 999-day threshold criteria.
To resolve this, you should refactor or transition the scoring logic into an asynchronous process, such as a Queueable Apex job or a scheduled batch process, rather than letting it fire on immediate after-insert triggers from the payment portal. This decouples the GoFundMePro gift ingestion from the resource-intensive iWave scoring callouts, ensuring the donations sync cleanly first without being blocked by subsequent processing errors.
Additionally, review the error logs in your Setup under Apex Exceptions or Process Automation Failures to identify the exact failing element. Adding explicit null checks and bulkified try-catch blocks within your wrapper handler will also prevent third-party integrations from stalling when missing secondary related fields during creation.
