Changing URL of a page inadvertantly created an infinite loop that was resulting in a 503 error

I became aware of the issue because of a google search console notification. Digging through the Drupal logs I found a notice about an infinite loop involving a redirect with specific ID - when looking at the redirects in place, I saw that there was one in place for /demo => /demo. When I deleted this, the problem was resolved. We had a page that existed at /see-a-demo and we decided to change the URL to /demo. The module was set to automatically create redirects when changing the URL's on content, and somehow it created a redirect from /demo => /demo which you can't manually create, and was then causing a 503 error to fire when visiting /demo/

If you visited /demo without the trailing slash, it was fine.

At first I thought it was an issue with a service trying to load something else at that path, like a reserved folder name or something like that, because other url's with trailing slashes would redirect to the canonical url without the trailing slash, yet /demo/ did not redirect to /demo.

Not quite sure how to replicate the issue, but wanted to let you know that somehow the automation in the module created an infinite loop that was causing some issues.

Thanks