Storyline : File importing error - Storyline 360 couldn't find translations for ## string(s)

Feb 23, 2022

I have multiple new training projects and see the same "Completed with Exception - Storyline 360 couldn't find translations for 5 string(s)" errors with all projects.

The original training contents are in English. I have exported all contents in MS Word file and localized in Japanese. A missing string error occurs when I import the translated word file into the storyline. All file shows the same "5" missing strings.

I would appreciate it if anyone could assist me with this.

7 Replies
Jose Tansengco

Hello Ann,

I went ahead and created a support case for you so our support engineers can take a look at your project and translation files. Not all errors are caused by the same exact thing, so it will be best if we could take a look at your project files to figure out what's happening. Your case is in good hands!

Mike Anderson

When translating courses, your Storyline 360 project file and the exported Word document must have the same number of text strings. In other words, don't make any changes to your Storyline 360 project file after exporting it to Word for translation.

If there’s a mismatch between both files when you import the translated Word document back into Storyline 360, you'll see the following “Completed with exceptions” error. 

The actual number of exceptions varies based on the number of missing strings.

"Completed with exceptions" error message in Storyline 360

How to Fix It

To avoid this error, only modify text in the Translation column of the Word document.

However, it’s easy to fix the issue after it occurred! Simply export your Storyline 360 project to Word again, translate the new text strings, and reimport the document.