Scheduled runs for load tests with profiling data throw serialization exceptions and breaks load result
in some cases when load run with profiling is triggered, randomly null data is returned that cannot be serialized and serialization exception is thrown in log and load result reports wrong default data