[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

ACSD-64813: Unassigning categories in B2B shared catalog via REST API is slow

The ACSD-64813 patch fixes the issue where unassigning categories in a B2B shared catalog via the REST API is slow. This patch is available when the Quality Patches Tool (QPT) 1.1.65 is installed. The patch ID is ACSD-64813. Please note that this issue is scheduled to be fixed in Adobe Commerce 2.4.9.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.7-p3

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.4 - 2.4.8
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Unassigning categories in a B2B shared catalog via the REST API is slow.

Steps to reproduce:

  1. Enable B2B, Company, and Shared Catalog.

  2. Generate 30,000 active, in-stock products.

  3. Create a custom shared catalog and assign all products to it.

  4. Create a new category under the default root category and assign a few products to it.

  5. Use the admin token to call the REST API endpoint rest/all/V1/sharedCatalog/<shared_catalog_id>/assignCategories with the new category ID.

    code language-none
    {
      "categories": [
        { "id": <new category id> }
      ]
    }
    
  6. Confirm the response is true.

  7. Run bin/magento cron:run twice or perform a reindex.

  8. Use the admin token to call the REST API endpoint rest/all/V1/sharedCatalog/<shared_catalog_id>/unassignCategories with the new category ID.

    code language-none
    {
      "categories": [
        { "id": <new category id> }
      ]
    }
    

Expected results:

The operation should complete in a reasonable time (under a couple of minutes).

Actual results:

The execution takes about 30 minutes or results in a timeout error.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3