Hi @Mark Todorov 

I suggest verifying if your Linux pattern or the shared library pattern where this step resides is OOB and not customized.

If it's OOB and you still see this, it could be something specific to your env or a particular host. The above step has an EVAL script, and possibly due to some reason, the values are not populated for some variables, causing such errors.

I suggest debugging prior steps to know why some data is not fetched, which it has to ideally, leading to such an exception.

Usually, the whole discovery fails in such exceptions, which is expected behavior.