# Multiple instances on the same machine data collision. Modify used paths **URL:** \ **Category:** Meeting SDK\ **Created:** [March 4, 2026, 10:29am UTC](https://devforum.zoom.us/t/multiple-instances-on-the-same-machine-data-collision-modify-used-paths/142289 "2026-03-04T10:29:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![pavlon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/pavlon/32/50982_2.png) [@pavlon](https://devforum.zoom.us/u/pavlon)\ **Post date:** [March 4, 2026, 10:29am UTC](https://devforum.zoom.us/t/multiple-instances-on-the-same-machine-data-collision-modify-used-paths/142289/1 "2026-03-04T10:29:11Z")
### **Meeting SDK Type and Version** _6.7.5 Linux_ **Description** _Meeting SDK creates and uses folders on system like /var/.zoomsdk and_ /var/opt/zoomsdk. It is ok when I run single instance but when two at the same time, or when app is restarted I see SQL errors. Questions: 1. How can I run multiple Meeting SDKs on the same machine? 2. How can I modify folder paths that Meeting SDK uses? **Error** zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlcipher\_page\_cipher: hmac check failed for pgno=1 zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlite3Codec: error decrypting page 1 data: 1 zoom-bot-sample | 2026-03-04 10:08:33.977: ERROR CORE sqlcipher\_codec\_ctx\_set\_error 1 zoom-bot-sample | 2026-03-04 10:08:33.978: ERROR CORE sqlite3Codec: identified deferred error condition: 0 **How To Reproduce** _1. Launch 1st instance of app that uses Meeting SDK_ _2. Launch 2nd instance of app that uses Meeting SDK_ _3. Check logs_ ---
**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:** [March 5, 2026, 12:31am UTC](https://devforum.zoom.us/t/multiple-instances-on-the-same-machine-data-collision-modify-used-paths/142289/2 "2026-03-05T00:31:54Z")
Zoom’s Meeting SDK isn’t designed for multiple concurrent “instances” sharing the same machine state: it even defines[`SDKERR_OTHER_SDK_INSTANCE_RUNNING`](https://marketplacefront.zoom.us/sdk/meeting/linux/zoom __sdk__ def_8h_source.html), and [Zoom staff](https://devforum.zoom.us/t/meetingsdk-v5-16-0-is-now-unable-to-run-more-than-one-instance-in-the-same-user-session/95631/3) have called multi-instance workarounds (like `sdkPathPostfix`) **unsupported** and subject to breaking on upgrades. For something you can rely on, you’ll need to isolate each bot in its own container/VM (or separate host) so the SDK’s local files don’t collide. You could also consider using a [Meeting Bot API](https://www.recall.ai/product/meeting-bot-api?utm_source=zoom&utm_medium=forum_answer) or [Desktop Recording SDK](https://www.recall.ai/product/desktop-recording-sdk?utm_source=zoom&utm_medium=forum_answer) from Recall.ai, depending on whether you want bot-join or on-device capture. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [March 5, 2026, 1:55am UTC](https://devforum.zoom.us/t/multiple-instances-on-the-same-machine-data-collision-modify-used-paths/142289/3 "2026-03-05T01:55:43Z")
@pavlon since you are running Linux SDK, you would want to run them each in their own docker container for this scenario. ---
**Author:** ![pavlon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/pavlon/32/50982_2.png) [@pavlon](https://devforum.zoom.us/u/pavlon)\ **Post date:** [March 5, 2026, 12:31pm UTC](https://devforum.zoom.us/t/multiple-instances-on-the-same-machine-data-collision-modify-used-paths/142289/4 "2026-03-05T12:31:38Z")
@chunsiong.zoom @amanda-recallai thanks for your answers! What worked for me is setting different HOME env variable for each instance. No more errors like that. Checked 2 meetings in parallel and it worked.