Repository navigation
Bulk API limits - ACCS-703 - #564
Merged
Merged
Conversation
Contributor
Author
|
Product and engineering are still reviewing the exact limitations |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
jhadobe
marked this pull request as ready for review
October 1, 2026 16:12
jhadobe
added
hold for release
and removed
blocked
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
keharper
approved these changes
Oct 5, 2026
| Cron jobs are the default mechanism for [managing message queues](https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/message-queues/manage-message-queues) and starting message queue [consumers](https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/message-queues/consumers), but you can also use external process control systems (like [Supervisor](https://supervisord.readthedocs.io/en/latest/)) to monitor process management. You can use the [`bin/magento queue:consumers:start async.operations.all`](https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/start-message-queues) command to manually start the `async.operations.all` consumer that handles asynchronous and bulk API messages. However, manually starting consumers is not recommended because it requires you to keep your terminal session connected. | ||
| <InlineAlert variant="info" slots="text"/> | ||
|
|
||
| In Adobe Commerce as a Cloud Service, Bulk API limits are determined by the **Maximum Entities per Bulk Request** setting in the [Store Configuration](https://experienceleague.adobe.com/en/docs/commerce-admin/config/general/bulk-api). |
Contributor
There was a problem hiding this comment.
Move this to precede line 14, getting rid of the duplicate mentions of ACCS
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds notes to the Bulk Endpoints and API Security pages to explain the Bulk API limits for ACCS.
The links included will fail until this Admin PR is published.
Purpose of this pull request
This pull request (PR) documents how Bulk API limits work in Adobe Commerce as a Cloud Service (ACCS-703). In Adobe Commerce as a Cloud Service, the Maximum Entities per Bulk Request setting in the Admin Store Configuration controls the limits. PaaS deployments still configure limits in
webapi.xmlandwebapi_async.xml.Changes:
Affected pages
whatsnew
Updated Bulk endpoints and API security to explain that the Maximum Entities per Bulk Request Store Configuration setting controls Bulk API limits in Adobe Commerce as a Cloud Service.