Allure report shows wrong result when executed in parallel.

[ansans81]

Describe the bug

Allure report shows the same result as the previous run when jest is executed in parallel more. Every this is working if executed with -i flag

To Reproduce

Sample jest-based automation framework(Selenium) and use this library for allure reports.
Automate multiple flows that have the probability of pass or fail.
execute first run in a serial mode that is with -i.
Then execute same without -i and add --maxworker=4 flag to force parallel execution.
even we can try adding additional workflow before the parallel run. Even though it new run is identified the result with be the same, even if we add new workflows to the execution total test will remain the same in allure.
In the console, everything shows the correct result.

Expected behavior

Behavior should be the same even in the case of parallel and serial execution

Screenshots

Console result

Allure result for same run (Run number 25)

You can see the run from 15 to 22 was also parallel runs and we were getting the same result. but the actual case was different