Troubleshooting

Crowdin token not found

Typical error:

No API token found

Check one of these:

Then verify:

cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --status

Check:

Then retry:

./scripts/crowdin-sync.sh --push
./scripts/crowdin-sync.sh --pull

Check whether translators actually produced content for that locale.

Expected output paths look like:

If the locale is empty or missing, the issue is usually upstream in Crowdin, not in Astro.

First make sure the translated markdown exists in the repo.

Then redeploy from the cms jail project:

cd /usr/home/<tenant>/<tenant>-site
npm run deploy

If that succeeds, verify the live route with curl.

Remember the current runtime path is:

Not:

If an error message or an old note points at astro-docs, treat it as historical guidance and switch back to the current cms-jail path.

Check whether the translated markdown was actually pulled into git before deploy:

cd /home/<agent>/clawdie-ai
git diff -- docs/public/sl docs/public/de

If there are no new locale changes, the deploy is probably working and the content simply was not updated yet.

That should not happen anymore.

The current docs deploy path protects:

If tenant-site output was still removed, inspect the deploy script in the Astro project and confirm the protected-path behavior is still present.