Good catch! will will take care of this in a future release.
I generally use local variables within translator input and output because they are private. If I need to use a global I then assign the global variable based on the local variable I used. I take great care to limit the use of writing global variables to ensure two translators are not trying to write to them at the same time. With MT Pro, there optimization that allows some actions to occur in parallel in the interst of speed.
Bome Customer Care
Also available for paid consulting services: email@example.com
Thanks Steve. Also, perhaps a corollary issue is that ‘Dump Variables’ don’t show all the global z variables, despite being z variable being set. Oddly, some of them show on ‘dump variables’ but not all.
Yes, I typically also use local variables. This particular use case requires data be shared events and between translators (which I understand require the use of global variables).