# ICS importer deduplication and bump behaviour via API

**URL:** https://meta.discourse.org/t/ics-importer-deduplication-and-bump-behaviour-via-api/385379
**Category:** Development
**Created:** [October 11, 2025, 3:45pm UTC](https://meta.discourse.org/t/ics-importer-deduplication-and-bump-behaviour-via-api/385379 "2025-10-11T15:45:42Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [October 11, 2025, 3:45pm UTC](https://meta.discourse.org/t/ics-importer-deduplication-and-bump-behaviour-via-api/385379/1 "2025-10-11T15:45:42Z")

</div>

Deos discourse still bump the topic if first post in a topic is edited via REST API and the parameter `bypass_bump` is `false`?

---

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [October 12, 2025, 12:35pm UTC](https://meta.discourse.org/t/ics-importer-deduplication-and-bump-behaviour-via-api/385379/2 "2025-10-12T12:35:41Z")

</div>

the answer is no, however for [my script](https://meta.discourse.org/t/ics-discourse-importer/381646) it deosn’t matter because without `--time-only-dedupe` , a location change creates a new topic which obviously gets bumped in latest 🙂

---

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [January 8, 2026, 3:32pm UTC](https://meta.discourse.org/t/ics-importer-deduplication-and-bump-behaviour-via-api/385379/3 "2026-01-08T15:32:20Z")

</div>

I noticed the recent request specs added in [DEV: Add bypass\_bump parameter to post update API by ZogStriP · Pull Request #36976 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/36976) explicitly cover `bypass_bump` being omitted vs set to false.

In particular, the bumping asserted there is for wiki posts, which makes sense given their existing exception, and helped clarify that `bypass_bump=false` is “allow default behaviour” rather than a positive bump signal.

That aligns with my reading that for non-wiki posts, false is effectively non-actionable under the current “no bump on edit” behaviour.