While setting custom URL slugs in Apidog, I’m encountering the error message:
“Same URL already exists, please modify”,
even though there is no existing endpoint in the project using that URL slug.
Initially, this issue didn’t exist. However, after I deleted a folder containing some endpoints, I started seeing this error when trying to reuse the same slugs from the deleted endpoints.
When deleting the folder, a message is displayed that the folder and endpoints would be moved to Trash and permanently deleted after 30 days. To resolve this, I also went ahead and manually deleted the folder from Trash, but the issue still persists.
It seems the system might still be retaining the slug references internally, which is blocking me from reusing them.
Hi, thanks for the update. I have updated to the latest version
I noticed that in that folder, the endpoints directly inside it were updated successfully with URL slugs.
However, subfolders within that same folder contain endpoints that are showing the error:
“Same URL already exists, please modify”, even though these slugs are not used anywhere else in the project. It seems the issue might still be affecting endpoints located in nested folders.
I’m sorry we couldn’t reproduce the issue. Could you please share a screenshot? Normally if a slug exists, it would show “This slug is already in use by:xxx” as shown in the image below.
I’m only getting the message “Same URL already exists” without any endpoint navigation, even though there’s no existing endpoint with the same slug.
This started happening after I deleted the endpoints (in a subfolder) that originally had this slug. It seems like the slug is still reserved internally despite the deletion.
Could you please refresh and try again? If the same slug still appears to exist, try accessing the documentation site with that slug to check which endpoint/folder it corresponds to.
We’ve been facing the same slug issue for quite some time now, and despite trying all the suggested steps (refreshing, version update, etc.), the issue is still unresolved. This is directly affecting our documentation site. Please provide a proper solution as soon as possible, it’s quite urgent now.
