Issue:
Recently I had an issue where I was getting a "Not Serializable Exception" when building a pipeline job (totally understandable error) caused by a LazyHashMap. I needed to just change the type of variable I was storing in order to make it serializable for CPS. The issue was that this was being stored as a ENV variable rather than a groovy variable and therefore threw an error on a very different step (in this case it was a email ext step) and was difficult to track down.

Request:
Would it be possible to get variable names or a pointer to the actual variable which threw the serialization error? That would be very helpful in the error message so I can find where it was potentially set much earlier and can be corrected