Mass actions silently process only a subset of selected products due to max_session_size_admin limitation

[hnsr]

Preconditions (*)

1. Magento 2.4.3
2. Catalog size of ~18k products (I estimate this issue will occur starting at around 10k products)

Steps to reproduce (*)

1. From the product grid, 'Select All' products
2. From the Actions drop-down, select 'Update Attributes'
3. Change any attribute (this step is technically not needed, the error is triggered at the above step when IDs are submitted)

Expected result (*)

1. All products are processed

Actual result (*)

1. Only subset of the selected products are processed
2. When examining the message on the queue, it shows only a few product SKUs
3. When examining the system.log file, a log entry such as [2021-12-22 12:41:14] main.WARNING: Session size of 498864 exceeded allowed session max size of 256000. appears when submitting the chosen mass-action

Everything works as expected when the max_session_size_admin setting is increased to an appropriate value, but I feel this should be handled a bit more graciously, or perhaps the selected IDs should be passed through the request body instead of the admin session.

The docs do mention that an error is meant to be shown to the user when the limit is exceeded (see https://docs.magento.com/user-guide/stores/security-session-management.html#admin-session) but that does not appear to happen in this case. (I would argue that the error mentioned in the documentation is not particularly helpful either)

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [x] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @hnsr. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-Hotel. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hi @hnsr, Thank you for reporting the issue. We have tried this issue on Magento 2.4-develop and we have successfully reproduced it.

Steps followed to reproduce issue:

1. Installed the clean Magento 2.4-dev

2. Created 20000 plus products.

3. From the product grid, 'Select All' products

4. From the Actions drop-down, select 'Update Attributes'

5. Try to change any attribute and observe the error message.

6. On the admin panel, Magento shows the error message - “Please select products for attributes update.” (See the attached screenshots)

7. Observe the error logs - “[2021-12-23T13:01:20.142748+00:00] main.WARNING: Session size of 847601 exceeded allowed session max size of 256000.”

The error message that appears in the admin panel is irrelevant and difficult to understand the actual issue also it is not as per the Magento documentation. Hence confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2045 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[hnsr]

Hi @engcom-Hotel , thanks for confirming!