Hi kevin spence 

Unknown said:

is there a simple way to get this info from the error log that appears after the batch task is completed or fails please?

As Evzen said, there isn't an easy way to tackle this I'm afraid.

Unknown said:

I really wish that the developer/manager responsible for this terrible functionality spends at least a month dealing with such problems at least ten times a day... Perhaps THEN they will finally realize what crap they created :-\

I hope it doesn't take this for us to realise the difficulties our users sometimes have.  However, the next CU, due very soon, will come with some enhanced logging that will send back error details to development so they will start to experience the sort of things our users see first hand, and in some cases the frequency in which they can occur.  So this is a good thing, and whilst they are unlikely to provide every detail we need to fix things they should start to help us focus efforts in the right place and where they will do the most good.  This is a step ion the right direction.

Unknown said:

However, the next CU, due very soon, will come with some enhanced logging that will send back error details to development so they will start to experience the sort of things our users see first hand, and in some cases the frequency in which they can occur.

Well, if that CU won't fix all the showstoppers (like the broken segmentation), many of us using Studio in way more advanced way than common translators, won't use it anyway... so the devs still won't get the info.

Which leads me to a sarcastic note I simply can't resist making: Oh, enhanced logging "already" at the end of 2017... wow...

Unknown said:

This is a step ion the right direction.

Definitely, no doubt about that. Just too late...
Still, better late than never, that's for sure. ;-)

Unknown said:

However, the next CU, due very soon, will come with some enhanced logging that will send back error details to development so they will start to experience the sort of things our users see first hand, and in some cases the frequency in which they can occur.

Well, if that CU won't fix all the showstoppers (like the broken segmentation), many of us using Studio in way more advanced way than common translators, won't use it anyway... so the devs still won't get the info.

Which leads me to a sarcastic note I simply can't resist making: Oh, enhanced logging "already" at the end of 2017... wow...

Unknown said:

This is a step ion the right direction.

Definitely, no doubt about that. Just too late...
Still, better late than never, that's for sure. ;-)