When GP tool throws an error, indicate what row/ObjectID the tool got stuck on

[Bud]

When running geoprocessing tools, we sometimes get errors. There are lots of possible reasons for errors, but one of them is the tool got stuck on a specific feature. It would help if the GP tool indicated what row it got stuck on, such as including the ObjectID in the error text.

Related: GP tool to export one feature at a time and log problem features in an error table

[RichardFairhurst]

Using Python in the Field Calculator is notorious for this type of troubleshooting.  Knowing which row it failed on would speed up the process of correcting the Python expression or refining the record selection to avoid triggering the error and having the calculation stop working midway through the calculation.