Slug conflicts
Fix Smart Link save errors caused by a slug that is already in use somewhere in your organisation.
Use this guide when a Smart Link will not save because the Smart Link Slug is already being used.
When you need to find an existing link, the Smart Links Links view provides search and filters, and the Reports view helps compare links across the organisation. Open either from the left navigation.
Symptom
You create or edit a Smart Link, enter a slug, and OmniLab does not accept it because that public identifier is already taken.
Why it happens
Smart Link slugs need to stay unique across the whole organisation.
That means a folder does not create a separate namespace. Even if another Smart Link lives elsewhere in the folder tree, it can still block the slug you want.
How to fix it
Search Smart Links for the existing slug
Open the Smart Links library or Reports view and search for the slug or the likely Smart Link title.
This helps you confirm whether the existing link is still live, archived in practice, or simply named more generically than expected.
Decide whether you need a new slug or the old link
If the existing Smart Link is still in use, create a different slug.
If the old Smart Link is no longer needed, disable it first, confirm nobody still relies on it, and only then delete it.
Save a clearer replacement slug
Use a short alternative that stays readable and unique, such as:
spring-launch-poster-frspring-launch-food-courtspring-launch-email
How to avoid repeated conflicts
- decide on one organisation-wide slug naming style
- include the placement or channel when several links point to similar destinations
- keep old test links disabled and cleaned up once they are no longer needed
- use folders for organisation, but never rely on folders to make a slug unique