Start with one short instruction you know and one target language. Editor interface language and instruction content language are separate choices: English application menus do not prove that the workflow instructions have been translated. Check the title, description, media, and fields in the operator view in the target language.
The workflow's content language and the application's interface language are different concerns. Changing the language you are authoring does not mean every catalog item or interface label is being translated.
Translate a step
Select the step and open Basic Info.
Use the translation bar to choose the target content language.
Enter the translated Title and Description.
Save and review the result in that language.
Repeat for the instructions the operator will use.
The selector sits above the instruction’s Title and Description. This example’s default content language is Hebrew, with English available as a target; application menus remain English.
Confirm the intended languages are enabled for the workflow/environment before starting.
Use the translation actions
The translation bar has its own actions menu.
Overwrite Content can copy source content into a non-default language. Review existing translated text before using it; copying source text is not a finished translation.
Where available, Machine Translation provides a starting translation for a non-default language. Review terminology, units, product names, and safety-critical instructions.
Mark a reviewed non-default translation complete using Mark as Complete. From the default-language context, use the available incomplete action when the translations need another review after a source change.
A completion marker is an editorial status, not proof that a qualified person checked the technical meaning.
Fields and shared content
Field titles, help text, and options have their own translation data. Check them separately; translating the step description does not automatically translate every field or List Item.
Catalog items displayed by the editor can follow the application/interface language. Do not use their appearance alone as proof of the operator's content-language behavior.
Review with an operator view
Preview the workflow in the intended language and check:
Titles, descriptions, and media context.
Data-field titles, help, and choices.
Variable values inserted into instructions.
Branch labels and any missing/fallback text.
Text direction and readability where relevant.
Test both a normal and an alternative route. A translated start step does not establish that a hidden or failure-path instruction is ready.
AI Assistant versus machine translation
An assistant request can propose broader edits. Review its proposal rows and approval behavior separately from the translation bar's Machine Translation action. Approving an assistant row applies that operation; always inspect the changed content afterwards.