if you miss a generated variants or result data of a variant is not correct, this could be come up
with an issue in getting the new variant number for a new generated configuration.
When reading this note, you shouldn't fall into panic. This problem only occurs when very, very much configurations are generated at the same time or very quickly. So... if 2 processes randomly request a new variant number almost simultaneously in a timeline of milliseconds.
From Beas version 2023.04.00.10 the logic for generating the variant number is totally revised and this issue is not possible any more.