Duplicate Recording ID

I am having an issue where the /api/recordings/start API endpoint will sometimes return the same ID more than once for the same session. It doesn’t happen consistently even when testing with the same exact steps… start a session, participant joins, start recording, stop recording, start recording again. On the 2nd start of recording after stopping, sometimes the returned ID will be the same as the one from the 1st call to start recording.

Is this to be expected or should the IDs always be unique?

This is probably a concurrency problem.

We will take a look.

Hi Micael. Any update on this? Thanks.

Please can you share with us OpenVidu server logs when bug is reproduced? In that way, it is easier for us to spot the issue and solve it.

I’m not able to reproduce it now. If I see it again I’ll let you know. Thanks.

We plan to address several recording bugs related with concurrency in the following days.

We let you know the progress.

Hello there,

I’ve trying to replicate the issue, but I’m not able to do so. It shouldn’t be a concurrency problem, as no recording shall be initiated for a session that is already being recorded, and the ID is the first thing generated when initializing the recording, so it is available even before stopping the recording becomes an option.

I haven’t seen this issue in a while so it may have been fixed already. I’ll let you know if I see it again. Thanks.