Resolve custom-slug conflicts and limits
Reserved names, legacy-address conflicts, already-used/concurrently claimed slugs, organization slug limits, and retiring older history before another rename. Link Tree editor permission required.
Der redaktionelle Inhalt dieses Artikels ist derzeit auf Englisch verfügbar. Die Navigation des Hilfe-Centers ist lokalisiert.
Überblick
Reserved names, legacy-address conflicts, already-used/concurrently claimed slugs, organization slug limits, and retiring older history before another rename. Link Tree editor permission required. Use this guide to isolate the cause safely before repeating the action. FoxLink manages tracked Short Links, versioned Link Trees, public aliases, redirects, analytics, and destination health.
Identify the symptom
Reserved names, legacy-address conflicts, already-used/concurrently claimed slugs, organization slug limits, and retiring older history before another rename. Link Tree editor permission required. Note the exact point where the actual behavior differs from what you expected.
Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.
Checks to make in order
Start in FoxLink Dashboard in the organization navigation. Keep the affected item open where possible so you can compare the state after each check.
- Check 1: Reserved names
Review reserved names and choose the value that matches your intended result.
- Check 2: Legacy-address conflicts
Review legacy-address conflicts and choose the value that matches your intended result.
- Check 3: Already-used/concurrently claimed slugs
Review already-used/concurrently claimed slugs and choose the value that matches your intended result.
- Check 4: Organization slug limits
Review organization slug limits and choose the value that matches your intended result.
- Check 5: Retiring older history before another rename
Review retiring older history before another rename and choose the value that matches your intended result.
- Check 6: Link Tree editor permission required
Review link Tree editor permission required and choose the value that matches your intended result.
Safe recovery
After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when the Short Link or Link Tree shows the intended draft, published, redirect, analytics, or health state.
If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.
- Verify the FoxLink add-on and the separate Short Link or Link Tree view/edit permission required by the action.
- Check custom-slug format, reserved names, active history, and concurrent edits before retrying a save.
- For public links, distinguish a missing 404 response from a permanently retired or deleted 410 response.
If you still need help
Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.
Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.
Verfügbarkeit und Zugriff
Die Verfügbarkeit hängt von deinem Organisationszugriff und deinen Berechtigungen ab.