Any completed localization job can now be retranslated from the dashboard with one click. Until this week, if a job came back wrong – stale glossary, mid-flight prompt change, model regression – your only options were to file a ticket or re-run the entire upstream batch. Now the job page itself has the trigger.
Also shipped#
- Outbound payloads are chunked. Big jobs no longer hit Worker memory limits.
- JSONC support as a source format. Files with comments and trailing commas now parse.