# Platform Release 340 - October 2025

**URL:** <https://community.tulip.co/t/platform-release-340-october-2025/15704>\
**Category:** Announcements\
**Created:** [October 8, 2025, 10:21pm UTC](https://community.tulip.co/t/platform-release-340-october-2025/15704 "2025-10-08T22:21:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![L\_Churchill](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/l_churchill/32/5200_2.png) [@L\_Churchill](https://community.tulip.co/u/L_Churchill)\
**Post date:** [October 8, 2025, 10:21pm UTC](https://community.tulip.co/t/platform-release-340-october-2025/15704/1 "2025-10-08T22:21:31Z")

</div>

🎉 Exciting news - Release 340 is here!

The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the [release notes](https://support.tulip.co/docs/platform-release-340-october-2025) and dive into what’s new.

Share your thoughts and questions below ⬇ 😊

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [October 10, 2025, 1:13am UTC](https://community.tulip.co/t/platform-release-340-october-2025/15704/2 "2025-10-10T01:13:47Z")

</div>

> _Added an instructional message when an app cannot be exported due to it referring to two tables with the same ID_

How could two different tables have same ID ?

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [October 10, 2025, 5:49pm UTC](https://community.tulip.co/t/platform-release-340-october-2025/15704/3 "2025-10-10T17:49:48Z")

</div>

Hello Aoki-san, this definitely surprised us as well! Tables in Tulip have multiple ID schemes with different purposes. In this case, we believe the root cause is unreliable behavior of the old import/export feature, which was creating duplicate tables in certain situations upon import. However, the trigger logic still pointed to the original copy of the table, so there is no data being sent to the wrong table. The new import/export infrastructure is more sensitive to ensuring there are never duplicates created.