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?
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.