# Connected app instances after ending Meeting

**URL:** <https://devforum.zoom.us/t/connected-app-instances-after-ending-meeting/72523>\
**Category:** Zoom Apps\
**Created:** [July 20, 2022, 12:23am UTC](https://devforum.zoom.us/t/connected-app-instances-after-ending-meeting/72523 "2022-07-20T00:23:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose.jassojr](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose.jassojr/32/32818_2.png) [@jose.jassojr](https://devforum.zoom.us/u/jose.jassojr)\
**Post date:** [July 20, 2022, 12:23am UTC](https://devforum.zoom.us/t/connected-app-instances-after-ending-meeting/72523/1 "2022-07-20T00:23:24Z")

</div>

Hi, I use `connect` while using the app in a meeting/webinar which opens an instance of the app in the main client in the background. After ending the meeting, that main client app instance that was in the background pops up. Is there any way to prevent that? I call `connect` in the first place in the case of the app first being started in the main client then the meeting so that way I can maintain state in case the main client app instance is closed.

---

<div class="post-metadata">

**Author:** ![narmadaravali](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/narmadaravali/32/39496_2.png) [@narmadaravali](https://devforum.zoom.us/u/narmadaravali)\
**Post date:** [July 20, 2022, 4:09pm UTC](https://devforum.zoom.us/t/connected-app-instances-after-ending-meeting/72523/2 "2022-07-20T16:09:59Z")

</div>

The idea behind `zoomSdk.connect` is to carryon state to out-of-meeting instance after meeting ends. That’s an expected behavior.
