Query Salesforce Big Objects with SOQL-style async queries and understand the indexing constraints
domain: developer.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Define a Big Object with a custom index composed of multiple fields using the Metadata API or Setup UI
Use the standard Salesforce REST query endpoint but note that only equality and range operators on indexed fields are supported
Submit an async SOQL query via the Async Query endpoint at /services/data/vXX.0/query/ adding Sforce-Query-Options headers for async mode
Poll the query job status and download results once the job completes
Insert Big Object records directly using Apex Database.insertImmediate() which bypasses triggers and does not call standard DML
Plan data archival by writing completed transaction records from standard objects into the Big Object via scheduled Apex
Known gotchas
Big Objects do not support UPDATE or DELETE; records are immutable once inserted, so incorrect records require inserting a corrective record and filtering in queries
Queries must be ordered by and filter on the Big Object's custom index fields in the exact order they were defined; out-of-order field references cause a query error
Standard Salesforce triggers, workflow rules, and flows do not fire on Big Object inserts; all processing logic must be handled before calling insertImmediate
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?