Troubleshooting Ingest Timeouts

Solve issues encountered with Bulk API 2.0 ingest operations.

To troubleshoot an ingest timeout error, try the following suggestions:

Check your payload.
- Check CSV formatting. Prepare CSV Files
- Check Date formatting. Valid Date Format in Records (2.0)
- Check Relationship fields. Relationship Fields in a Header Row (2.0)
- Check that compression is gzip format. Use Compression for Bulk API 2.0 Ingest Responses
- Check that your data is organized to prevent lock contenttion. Organize Data to Minimize Lock Contention
Create a new ingest job with only the failed and unprocessed records.
- To get the failed records, use Get Job Failed Record Results.
- To get the unprocessed records, use Get Job Unprocessed Record Results.
Divide the job into smaller jobs.
- Creating smaller requests may help to isolate problems in one or more jobs.
Review your custom logic, such as triggers or flows.
- Non-optimized custom logic can contribute to timeouts. In order to speed up insert, update, or delete operations, make sure triggers or flows are optimized. Consider temporarily disabling triggers or flows that are non-essential.

Organize Data to Minimize Lock Contention

To minimize the potential for lock contention, consider pre-organizing your data when planning your Bulk API 2.0 data loads.

See Also