@blue-exabyte-41111 afaik this should be fixed in harvester 1.2.0 which should hopefully be out in not too long, see https://github.com/harvester/harvester/issues/4057 and related issues