Limitations

• Only super admins, admins, and developers can use this API.
• Only one bulk write job can be active per form. You cannot create a new job until the current job status is marked as Completed, User Aborted, System Aborted, or Failed.
• The input file must be a csv file, or a zip file containing a csv file, and must not exceed 100 MB.
• After uploading an input file, you cannot re-upload or replace it. To use a different file, you must:
  • Abort the job using the start/abort job API
  • Create a new bulk write job
  • Upload the new input file
• The input file is deleted 3 days after upload.
• A job must be started within 3 hours of creation. Otherwise, its status will be marked as Expired.
• A bulk write job starts execution only when its status is updated to Start using the start/abort job API.
• The result file is available for 3 days after the job status becomes Completed, User Aborted, System Aborted, or Failed. After this period, the job expires.
• Bulk write jobs are not supported for on-premise setups.
• Records are processed in batches of 200. If more than 5% of the total batches fail, the job status is marked as System Aborted.
• Workflows will not be executed for the records that are inserted using bulk insert API.
• The formula field and barcode field will be computed asynchronously.