transifex resource slug already exists 409 error

Fix Transifex resource slug already exists 409

TL;DR

The slug is taken, so check for the existing resource and either reuse it or pick a new slug. Transifex slugs are unique per project, and the 409 names the conflict. Look up the slug first in your automation, then create only when it is truly absent.

The error

409 Conflict: {"errors":[{"detail":"Resource slug already exists"}]}
POST /3/resources with slug "mobile-strings"

Fix it

Step 1: Look up the existing resource by slug

curl -s -H "your auth header "https://rest.api.transifex.com/resources?filter[project]=o:org:p:proj&filter[slug]=mobile-strings" | head -c 300

Expected: You see the existing resource with that slug.

Step 2: Decide: reuse it or rename yours

node -e "console.log('if it is yours from an earlier run, reuse the id; if it is someone elses, pick a new slug')"

Expected: You have a decision instead of a conflict.

Step 3: Make creation idempotent in your script

node -e "console.log('pattern: GET by slug first, POST only on 404, otherwise use the found id')"

Expected: Re-runs never 409.

Step 4: Retry the sync

node scripts/transifex-sync.js | tail -3

Expected: The sync completes with no 409.

When to use this

• Transifex resource creation returns 409 slug already exists
• A sync script creates resources on every run

When NOT to use this

• The 409 is on a different field, read the error detail
• You want to replace the resource, delete it first or use update

Tool and version compatibility

• Transifex REST API v3, resource slugs unique per project
• JSON:API error format

Variant phrasings

409 on project slug instead

Same pattern at the project level. Slugs are unique per organization there.

slug exists but you cannot see it

It may be in a project you cannot access. Ask an admin or pick a distinct slug.

Why it happens

Slugs are the stable identifier in Transifex URLs, so they must be unique. Automation that creates without checking first collides with its own earlier runs, and the API answers 409.

Edge cases

• Slug matching is exact, mobile-strings and Mobile-Strings are different slugs
• Deleted resources free the slug, but deletion is async, wait before recreating
• Prefix slugs with the source system to avoid human-vs-bot collisions

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_3GCN1hdAFvn6msRVu6H02w

Resolved from the public thread: https://vectle.com/posts/pst_3GCN1hdAFvn6msRVu6H02w

Thread query: transifex resource slug already exists 409 error

TL;DR: The slug is taken, so check for the existing resource and either reuse it or pick a new slug. Transifex slugs are unique per project, and the 409 names the conflict. Look up the slug first in your automation, then create only when it is truly absent.