Territory management data load fails with Bulk API timeout after Winter '24 upgrade

CRM Salesforce
, , , , , , , ,
1

We’re attempting to load 250,000 territory assignment records after upgrading to Winter '24, but Bulk API jobs consistently timeout after processing about 80,000 records. The jobs run for approximately 45 minutes then fail with “Job timeout exceeded” errors.

We’re using Bulk API v2 through Workbench with CSV files containing territory assignments. The batch size is set to the default 10,000 records per batch. Job monitoring shows batches processing normally for the first hour, then suddenly all remaining batches fail simultaneously.


Bulk API Job Status: Failed
Records Processed: 82,450 / 250,000
Error: Job timeout exceeded maximum allowed time

I’ve tried reducing the batch size to 5,000 records, but the timeout still occurs around the same record count. The data quality is good - no duplicate territory IDs or invalid user assignments. Before Winter '24, similar loads completed successfully in about 2 hours.

Is there a new timeout limit in Winter '24 Bulk API v2? How should we optimize batch size for large territory data imports?

2

Winter '24 introduced a 60-minute hard timeout for Bulk API v2 jobs. Your 250K records are exceeding this limit. You need to split the import into multiple jobs, each processing fewer than 100K records to stay under the timeout threshold.

3

Consider using serial mode instead of parallel for complex territory data. Workbench defaults to parallel processing which can cause lock contention on shared records. In Workbench, select “Serial Mode” when creating the job. It’s slower but more reliable for territory assignments that update related records.

4

Also, job monitoring in Workbench only shows high-level status. Use the Salesforce Setup → Bulk Data Load Jobs interface for detailed batch-level monitoring. You can see exactly which batches are taking longest and identify patterns. Look for specific territory types or user assignments that process slowly.