Skip to main content

Troubleshooting

I can't see /tags or any of its sub-pages​

You probably don't have tag:read on the current workspace. Switch workspaces or ask an administrator to grant the role.

"Vocabulary with key X already exists" when creating​

A vocabulary with the same key already exists in your scope (workspace or tenant) — even if soft-deleted. Either:

  • Pick a different key, or
  • Restore the existing vocabulary if it was deleted (admin only).

"Source or target tag not found" when merging​

One of the tags you're trying to merge has been deleted, or it belongs to a different workspace than the one you're in. Refresh the list and confirm both ids are still valid.

"Tags must be in the same vocabulary to merge"​

Cross-vocabulary merges are intentionally blocked. If you want to consolidate tags from two vocabularies, first move the source tag to the target's vocabulary (you need tag:manage), then merge.

/tags/templates is empty​

Your tenant or workspace administrator hasn't seeded any templates yet. Templates are workspace vocabularies with kind: TEMPLATE. Ask an administrator to create one — see Templates.

Bulk operation says "0 entities matched"​

Your filter set is more restrictive than expected. Check:

  • The entity type filter (often defaults to one type).
  • The "currently tagged" filter (only entities already having a tag are matched if you set one).
  • The workspace filter (you may be in a different workspace from where the data lives).

Analytics chart is blank​

The most common causes:

  • Time range is too short for any activity.
  • You're filtering on a vocabulary or entity type with no assignments.
  • You don't have tag-analytics:read.

Search uses the tag's key, label, and translations for the active locale. If the tag was created without translations and you're using a non-English locale, search may miss it. Add a translation under /tags/:tagId → Translations.

Things look broken after a deploy​

If pages load but actions fail with cryptic errors, the gateway may be serving an outdated schema. Wait a few minutes for schema propagation, then hard-refresh the browser (Ctrl+Shift+R / Cmd+Shift+R).

Reporting a bug​

Use the in-app feedback button or open an issue with:

  • The route you were on (e.g. /tags/list).
  • A screenshot.
  • The request id from the network tab if available (header x-request-id).
  • Whether the issue is reproducible.