Cannot create category schedule as it throws "error: : URL key for specified store already exists." error

[adarshkhatri]

Preconditions and environment

• Magento version: 2.4.6-p1 Commerce

Steps to reproduce

Create a category with this level:
Example tree (IDs are example purpose only)

Root Category (ID: 72)
        |- My Category (ID 75)
                    |- My Sub category (ID: 100)
                                   |- My sub sub category (ID: 300)

1. Now go to URL rewrite and filter by catalog/category/view/id/300 as the target path. Once found make a note of the request path (which will be something like: my-category/my-sub-category/my-sub-sub-category) and delete that item.
2. Now, create new custom URL rewrite:
   Request Path: my-category/my-sub-category/my-sub-sub-category
   Target Path: about-us OR any other CMS page
   Save it.
3. Go to category ID 75 and then try to create a schedule. It will throw error: : URL key for specified store already exists. error in the browser.

Expected result

System should allow me to save the schedule for that category.

Actual result

Error thrown on the browser: error: : URL key for specified store already exists.

Additional information

No response

Release note

No response

Triage and priority

• 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.
• 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]

Hi @adarshkhatri. Thank you for your report.
To speed up processing of this issue, 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

[m2-assistant]

Hi @engcom-Bravo. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://adfcbafe5383e2c0641595cfc6e16f5d.instances-prod.magento-community.engineering
Admin access: https://adfcbafe5383e2c0641595cfc6e16f5d.instances-prod.magento-community.engineering/admin_17bc
Login: 3032ae1e
Password: 8b4ca152072a

[engcom-Bravo]

Hi @adarshkhatri,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop with EE edition instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

Create a category with this level:
Example tree (IDs are example purpose only)

Root Category (ID: 72)
|- My Category (ID 75)
|- My Sub category (ID: 100)
|- My sub sub category (ID: 300)

• Now go to URL rewrite and filter by catalog/category/view/id/300 as the target path. Once found make a note of the request path (which will be something like: my-category/my-sub-category/my-sub-sub-category) and delete that item.
• Now, create new custom URL rewrite:
• Request Path: my-category/my-sub-category/my-sub-sub-category
• Target Path: about-us OR any other CMS page
• Save it.
• Go to category ID 75 and then try to create a schedule. It will throw error: : URL key for specified store already exists. error in the browser.

We are able to save the schedule for that category.

Kindly recheck the issue in Latest Magento 2.4-develop instance with EE edition and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[konradszwed]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @konradszwed. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @konradszwed, here is your Magento Instance: https://adfcbafe5383e2c0641595cfc6e16f5d.instances-prod.magento-community.engineering
Admin access: https://adfcbafe5383e2c0641595cfc6e16f5d.instances-prod.magento-community.engineering/admin_c3d6
Login: 187caad4
Password: b0ed037a7515