Error: ORA-30006 Resource Busy When Creating Campaign Member via Web-to-Lead

Root Cause

This error occurs when two or more processes attempt to update the same Campaign object at the same time. When a Web-to-Lead submission triggers Campaign Member creation, Salesforce locks the Campaign object briefly to ensure accurate rollup summary fields (RSFs) are calculated. If another process — such as a second simultaneous lead submission, a bulk import, a Data Loader operation, or a manual hierarchy recalculation — is already holding that lock, the new operation must wait. If it waits too long, it times out and Salesforce sends the error notification email.

Resolution Steps

To reduce the frequency of this error, minimize overlapping processes that update the Campaign object during lead intake.

1. Review scheduled jobs, Data Loader operations, and bulk imports to identify any that run concurrently with active Web-to-Lead form submissions.
2. Reschedule bulk Campaign updates (imports, hierarchy recalculations) to off-peak hours when Web-to-Lead traffic is lower.
3. If simultaneous high-volume Web-to-Lead submissions to the same Campaign are expected, consider splitting submissions across multiple Campaigns or staggering imports.
4. If the error occurs intermittently during normal traffic, it is typically self-resolving — the lead will be retried. Monitor the frequency and escalate to support if it occurs consistently.