Im using uitoolikt and with enabled cloud recording and working recording_completed webhook
Im running into issue when on same session I record multiple times.
If I record two times using start/stop recording button Im able to get my recording stored and receive webhook. However if I do it 3 or more times → recording is not processed and its not stored on cloud.
I tried to wait at least 1m between recordings and also ending session but no change.
Is there some limit of recording? I have not found this information anywhere.
You do not sya where you are recording but I will expect it is the cloud.
There is no clear set of rules for recording into the cloud. But if you do make stops and restarts when in a session, it is likely that your later requests will lose priority and the recordings will take longer to be processed.
Have you checked if they come back after a few hours?
The more likely failure mode is that your third “start” is happening while the SDK still thinks recording isn’t fully Stopped, which can cause RECORDING_MISMATCH_STATE (7202) - make the button wait until the status callback is actually Stopped before allowing another start.
Another common gotcha is segment length: if some of those stop/start chunks are very short, Zoom can show “recording could not be generated because the recording time was too short” (so it looks like “no cloud file” and no completion event) - see this Video SDK thread.
recordings are processed and I am able to get them with API endpoint GET /videosdk/sessions/{sessionId}/recordings
Issue is with receiveng webhook recording_completed as it wont come in scenario when user (host) is clicking start/stop recording multiple times.
Issue to reprocude:
host and participant join session. host starts recording. host and participant has audio recorded. host stop recording. host start recording again and repeat this process multiple times.
actual result: webhook not received
expected result: webhook received
The 403 error was triggered by AWS WAF (Web Application Firewall) before the request even reached the backend Lambda/API Gateway.
When a recording contains multiple files, the webhook payload size increases. When it was larger than ~10 KB payload → Failure (403).
Adding new WAF rule to allow URI for zoom fixed the issue.
Can I just comment from experience that Zoom can drop processing of multiple recordings down the queue when you stop and start multiple times. Therefore later recordings can be slower to be processed by Zoom. I do not know the exact queue rules, this is just experience.