Skip to main content

Hello,

Went to add localization files to an engagement, forced into draft mode. Files kept returning an xliff error.

After a few attempts, I downloaded a new xliff file - noticed that the engagementId between the original (pre-launch) and the launched (so now in draft mode) are not the same engagementIds.

 

Stopped engagement, original files loaded without errors.

 

Is this the expected behavior?

 

 

Hi @lpicone , 

Thanks for posting!

Yes, this is an expected behaviour. The Engagement Id will be different when compared to the ID in downloaded file, you can see this difference whenever engagement is forced to draft mode. But, however this will not impact while uploading the xliff file for localisation.

When engagement is forced to Paused state, then both the edited and launched will have same Engagement ID’s. 

 Thank you. Have a good day 😊


Reply