Resolve custom-slug conflicts and limits
Understand why a preferred custom URL cannot be saved.
Overview
A slug can be unavailable because it is reserved, already claimed, part of legacy history, or retired permanently. Another editor can also claim a value while you are working.
Resolve the message
- Check the format
Use the allowed lowercase letters, numbers, and hyphens with the required length and endpoints.
- Read the conflict
Choose another recognizable value if the identifier is unavailable. Refresh after a concurrent-change message.
- Review history limits
If history has reached its limit, inspect older active aliases before deciding whether to retire one.
Do not retire casually
Retirement permanently breaks that old address and does not make it reusable. Check existing shares before using it to free space in history.
Availability and access
Availability depends on your organization access and assigned permissions.