We had a conference running with 2 participants and individual recording in progress. We stopped the recording but at the very same moment a third participant joined the conference. Stopping of the recording took more time than normally but it finally succeeded.
But: the duration of the recording in the meta data was set to 1606318020.335 which is more or less the current unix timestamp and not the real duration.
The third participant is included in the recording but only for a very short time and with the following offsets:
I can sometimes reproduce it, but beause it’s a matter of exact timing, I can not reproduce it everytime. Please try the following steps - perhaps a few times:
create a new session with two publishers
prepare a third publisher who is ready to join but do not join now
start individual recording and record some minutes (if the recording duration is long enough then the stop action will take longer and the chances to reproduce will be higher)
now stop the recording and immediately after calling the API to stop the recording (while waiting for the answer of the API call) join with the third participant
after success of the API stop method check the recording meta data and you will perhaps find the timestamp as “startTimeOffset” and/or “endTimeOffset” of the third publisher.