@Wahyu Triyantoro When the bitlocker process is interrupted in between either due to machine level issues like with TPM, or with the end user actions, the process starts again causing the service to generate multiple keys.
A valid key always be found by matching the Recovery ID in those scenarios. If you want to know in deep a support case might be a good way to investigate to understand what could have went wrong. Needs debug logs level analysis.
-----------------------------------------------------------------------------------------------------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.