Caching in Task Mode Versus Ad Hoc Mode
There is an important difference between the way caching occurs in task mode versus ad hoc mode. When you are translating a file in task mode—that is, as part of a workflow—WorldServer always uses the cached version of the segmented asset that is associated with the task. If the fingerprint changes in the source asset, WorldServer warns you about your asset being out of date, but continues using the cached version of the asset you are working on. This is done so things do not change underneath you as you translate an asset.
However, there is still the danger that you might pick up an existing cache when your workflow executes the Segment Asset action. To avoid this problem, your workflow should precede the Segment Asset action with the Clear Segment action, which clears the segment cache for the asset, forcing it to be re-segmented and re-scoped. Then, after the Segment Asset action runs, you can translate the asset without fear that the external changes to the asset might cause it to change during your translation session. Using Clear Segment has other benefits as well: in projects with multiple target languages, it avoids segments splits or merges being incorrectly applied across the multiple targets.
When you translate in ad-hoc mode—that is, outside of a workflow—the asset is not associated with a task, and will be re-segmented under you if someone modifies the asset or file type while you are translating.