# Multiple recording in one session

**URL:** <https://devforum.zoom.us/t/multiple-recording-in-one-session/140142>\
**Category:** Video SDK\
**Tags:** recording, video-sdk\
**Created:** [December 22, 2025, 2:00pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142 "2025-12-22T14:00:38Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomas3](https://avatars.discourse-cdn.com/v4/letter/t/aca169/32.png) [@Tomas3](https://devforum.zoom.us/u/Tomas3)\
**Post date:** [December 22, 2025, 2:00pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/1 "2025-12-22T14:00:38Z")

</div>

Hi,

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.

videosdk-ui-toolkit: 2.2.5-1

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [December 22, 2025, 2:42pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/2 "2025-12-22T14:42:35Z")

</div>

hi @Tomas3 ,

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?

all the best

John

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [December 22, 2025, 8:03pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/3 "2025-12-22T20:03:46Z")

</div>

[Creating a new file on every stop/start is expected](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062627), but it’s probably not the root cause here - Zoom’s documented limit is **way higher** ([150 files per live session](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062627)), so “3+” segments shouldn’t hit it.

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)`](https://marketplacefront.zoom.us/sdk/custom/web/enums/ExceptionCode.html) - make the button wait until the status callback is actually [`Stopped`](https://marketplacefront.zoom.us/sdk/custom/web/enums/RecordingStatus.html) 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](https://devforum.zoom.us/t/issue-with-recording-duration-in-zoom-video-sdk/113050).

Also note the webhook timing: the [`session.recording_completed` event fires when the recording becomes available](https://developers.zoom.us/docs/api/video-sdk/events/), so if processing is delayed you won’t receive it immediately even if the recording was captured.

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [December 23, 2025, 9:18am UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/4 "2025-12-23T09:18:35Z")

</div>

Hey @Tomas3

Thanks for your feedback.

Could you share some problematic session IDs with us for troubleshooting purposes?

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Tomas3](https://avatars.discourse-cdn.com/v4/letter/t/aca169/32.png) [@Tomas3](https://devforum.zoom.us/u/Tomas3)\
**Post date:** [January 7, 2026, 8:01am UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/5 "2026-01-07T08:01:50Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Tomas3](https://avatars.discourse-cdn.com/v4/letter/t/aca169/32.png) [@Tomas3](https://devforum.zoom.us/u/Tomas3)\
**Post date:** [January 8, 2026, 6:23am UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/6 "2026-01-08T06:23:22Z")

</div>

I did test recording with start/stop recording 3 times. between each recording I have waited 1m.  
sessionID: bkxWiGaBSWaDFaoxjuxdYg==

session start: 2026-01-08T06:04:18Z

expected: to receive webhook recording\_completed  
actual: no webhook received

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [January 12, 2026, 7:36am UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/7 "2026-01-12T07:36:03Z")

</div>

Hi @Tomas3

Sorry for the late reply.

> bkxWiGaBSWaDFaoxjuxdYg==

From our logs, we can see that the webhook was triggered, but when calling the endpoint URL, it returned an HTTP **403** response code.

Could you please help check the response on your side?

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Tomas3](https://avatars.discourse-cdn.com/v4/letter/t/aca169/32.png) [@Tomas3](https://devforum.zoom.us/u/Tomas3)\
**Post date:** [January 13, 2026, 12:54pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/8 "2026-01-13T12:54:08Z")

</div>

Thanks for info,

issue is resolved.

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.

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [January 14, 2026, 12:50pm UTC](https://devforum.zoom.us/t/multiple-recording-in-one-session/140142/9 "2026-01-14T12:50:16Z")

</div>

hi @Tomas3 ,

Looks like you are close to the answer.

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.

John
