# General Translation Integrations: Managing translations
URL: https://generaltranslation.com/en-GB/docs/integrations/storyblok/guides/managing-translations.mdx
---

title: Managing translations
description: "How to re-sync Storyblok stories with General Translation: this guide covers reusing existing translations and reviewing draft-only writes."
related:
  links:
    - /docs/integrations/storyblok/guides/translating-content
    - /docs/integrations/storyblok/guides/using-translated-content
    - /docs/integrations/storyblok/guides/configuring-storyblok

---

After your first run, use the Storyblok integration to keep translations up to date. Each run reads the latest draft, reuses existing translations, and writes the results back as a draft.

## Re-sync after content changes [#re-sync]

When a story's source content changes, run **Sync and apply** again for that story and its target locales. General Translation re-reads the draft, translates any new or changed fields, and updates the story's draft.

If the source story changes while translation jobs are still running, General Translation stops before writing and asks you to rerun **Sync and apply**, so it never applies translations that no longer match the source.

## Reuse existing translations [#reuse-existing]

Every **Sync and apply** run imports existing translations. General Translation reads the localised values already present in the story and reuses them instead of retranslating them, then only translates what is missing.

This keeps repeat runs fast and preserves values you have already reviewed or edited in Storyblok.

## Writes are drafts only [#draft-only]

From the Dashboard, translations are always written back to Storyblok as drafts. Nothing is published automatically, so you can review each language before it goes live.

To publish, open the story in Storyblok, review the target language, and publish it there.

## Review what was written [#review-writes]

The results summary shows **Draft writes** (the previewed field-level changes) and **Applied writes** (the changes written back to Storyblok). Use these counts to confirm the run affected the fields you expected.

Then open the story in Storyblok, switch to a target language, and review the translated draft. See [Using translated content](/docs/integrations/storyblok/guides/using-translated-content) for how translations are stored and fetched.
## Next steps

- /docs/integrations/storyblok/guides/translating-content
- /docs/integrations/storyblok/guides/using-translated-content
- /docs/integrations/storyblok/guides/configuring-storyblok