IntegrationIntermediatebulk-apierror-handlingpartial-success
Handle Bulk API 2.0 failed records retrieval and partial job success
Real World Scenario
Nightly Contact load job succeeds with 400 failed records buried in unprocessed CSV; sales starts day with missing leads.
Expected Answer
• Poll job state until JobComplete then fetch unprocessedrecords CSV
• Parse failed rows error message to Integration_Error__c staging
• Alert ops failed count exceeds 1% threshold
• Retry failed subset after fix not entire 500k job
• allOrNone false explicit for partial success acceptance
• Reconciliation successful count plus failed equals source count
• Automate failed record quarantine workflow steward review
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Poll job state until JobComplete then fetch unprocessedrecords CSV. Parse failed rows error message to Integration_Error__c staging. Pick based on your integration pattern and team capability. Bulk job JobComplete does not mean all records succeeded—always fetch unprocessedrecords. Balance speed of delivery with maintainability.
Architect Perspective
Bulk job JobComplete does not mean all records succeeded—always fetch unprocessedrecords.