Limitations of Bulk Operations on Entries

• You can publish or unpublish up to 100 entries in 10 languages across 10 environments at a time.
• You can export up to 10,000 entries in a single export. If you start more exports than can run at the same time, the extra exports wait in the queue until they can run.
• You can import one file of up to 50 MB at a time, and run one import at a time.
• You can select and delete up to 100 entries at a time.
• You can publish up to 10 localized entry versions across 10 environments at a time.
• When scheduling bulk publishing/unpublishing, the date cannot exceed 12 months from the current date.
• You can update the workflow stage for a maximum of 10 entries at a time, provided they share the same workflow and workflow stage.
• You can change the workflow stage of up to 10 selected entries to a common stage. For example, you can move entries in the “Ready for Review” stage to the “Complete” stage at once.
• Localized entry versions can only be deleted through the “Delete” modal of the master language entry. They cannot be deleted directly from the “Delete” modal of the localized entries themselves.
• When deleting entries in bulk from the entry list page, you cannot delete the corresponding localized versions of the selected entries.

Note If you need to increase these limits, contact our support team.

select all records runs a bulk action on every entry in the entries list rather than on a per-page selection. The following limits apply to it:

• A select-all action resolves a maximum of 10,000 entries. If the list holds more entries than that, only the first 10,000 entries are acted on.
• Select all records supports publish, unpublish, delete, and add to release. It is not available for workflow updates or export.
• Select all records applies to entries only. It is not available for assets.
• Contentstack resolves the list when the job runs, not when you make the selection, so entries that change in between can change the set that is acted on.
• Draft entries that have never been indexed are not resolved by a select-all action.
• The language, environment, and scheduling limits listed above apply to select-all actions as well.