Hi @rybkinevg. 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.

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

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

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

Hi @rybkinevg,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.kindly refer the screenshot.

We are getting response as null.could you please let us know if we are missing anything and please try to reproduce the issue in Latest 2.4-develop instance.

Thanks.

Hi, @engcom-Bravo !

Thanks for your reply, but I am confirming that the issue is reproducible in 2.4-develop, I will describe steps which I done:

1. I installed the fresh Magento instance from 2.4-develop branch
2. Passed basic installation steps (DB setup, install command, admin setup)
3. Created a new URL Rewrite with following values:

• Create URL Rewrite = Custom
• Request Path = test
• Target Path = test

4. I configured the request timeout to 1 min (60000 ms), screenshot taken from Bruno HTTP client:

5. I send the following request and waited for 1 min:

{
  route(url: "/test") {
    relative_url
  }
}

6. I added some debug info to the app/code/Magento/UrlRewriteGraphQl/Model/Resolver/AbstractEntityUrl.php::findFinalUrl:

    private function findFinalUrl(UrlRewrite $urlRewrite): UrlRewrite
    {
        $count = 0;

        do {
            $nextUrlRewrite = $this->findUrlFromRequestPath(
                $urlRewrite->getTargetPath(),
                (int) $urlRewrite->getStoreId()
            );
            if ($nextUrlRewrite) {
                $urlRewrite = $nextUrlRewrite;
            }

            if ($count > 30) {
                die('I am in an endless loop');
            }

            $count++;
        } while ($nextUrlRewrite);

        return $urlRewrite;
    }

7. I resend the route request:

UPD I also double checked that the route query resolver in 2.4-develop branch still extends from the AbstractEntityUrl class and calling the parent::resolve() method which has the findFinalUrl method where the problem with endless loop appears

@magento give me a 2.4-develop instance