Why is 'ORDER BY Id' mandatory in this framework?

Including 'ORDER BY Id' ensures deterministic page boundaries, preventing records from being skipped or duplicated as you move through result pages.

When should I use the Bulk API instead of REST pagination?

The framework recommends using the Bulk API v2 whenever you expect a query to return more than 50,000 records to ensure stability and efficiency.

What is the maximum OFFSET allowed in Salesforce queries?

Salesforce enforces a hard limit of 2,000 for OFFSET; for results beyond this, the skill switches to nextRecordsUrl pagination or Bulk API.

Does this skill help prevent Salesforce API limit exhaustion?

Yes, it includes safety rules and strategy selection logic specifically designed to prevent unbounded queries from exhausting your API quota.

How does the framework handle mid-range result sets?

For sets between 2,000 and 50,000 records, the framework utilizes REST nextRecordsUrl pagination, which the CLI handles automatically.

Salesforce SOQL Paging & Large Result Framework

Name: Salesforce SOQL Paging & Large Result Framework
Author: RevPalSFDC

byRevPalSFDC

•

Database Management

Manages high-volume Salesforce data extraction by implementing safe pagination strategies, LIMIT/OFFSET logic, and Bulk API workflows.

The Salesforce SOQL Large Result Paging Framework provides Claude with specific guidance on handling high-volume data queries within Salesforce environments. It enables the AI to intelligently choose between REST pagination, LIMIT/OFFSET clauses, and the Bulk API v2 based on expected record volume, effectively preventing API limit exhaustion and ensuring deterministic results through mandatory ID-based ordering. This skill is indispensable for developers and RevOps teams building reliable data export, migration, or synchronization workflows that must safely handle datasets exceeding the standard 2,000-record threshold.

Key Features

01Best practice guidance for avoiding common Salesforce OFFSET limitations

021 GitHub stars

03Safety enforcement for deterministic results using mandatory ID-based ordering

04Automated transition from REST API to Bulk API v2 for datasets over 50,000 records

05Dynamic paging strategy decision tree based on estimated record counts

06Pre-query size estimation workflows to prevent API timeouts and limit hits

Use Cases

01Optimizing RevOps reporting queries to handle large-scale record sets

02Building safe data migration scripts for high-volume Salesforce objects

03Automating multi-page data exports while maintaining API quota health

Key Features

01Best practice guidance for avoiding common Salesforce OFFSET limitations

021 GitHub stars

03Safety enforcement for deterministic results using mandatory ID-based ordering

04Automated transition from REST API to Bulk API v2 for datasets over 50,000 records

05Dynamic paging strategy decision tree based on estimated record counts

06Pre-query size estimation workflows to prevent API timeouts and limit hits

Use Cases

01Optimizing RevOps reporting queries to handle large-scale record sets

02Building safe data migration scripts for high-volume Salesforce objects

03Automating multi-page data exports while maintaining API quota health