# Meldingen activeren bij geplande categorie wijziging maar niet bij handmatige

**URL:** https://meta.discourse.org/t/trigger-notifications-on-scheduled-category-change-but-not-on-manual-ones/273931
**Category:** Feature
**Created:** [4 augustus 2023 om 07:59 UTC](https://meta.discourse.org/t/trigger-notifications-on-scheduled-category-change-but-not-on-manual-ones/273931 "2023-08-04T07:59:05Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Nacho\_Caballero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nacho_caballero/32/130189_2.png) [@Nacho\_Caballero](https://meta.discourse.org/u/Nacho_Caballero)
#### Post date: [4 augustus 2023 om 07:59 UTC](https://meta.discourse.org/t/trigger-notifications-on-scheduled-category-change-but-not-on-manual-ones/273931/1 "2023-08-04T07:59:05Z")

</div>

Continuing the discussion from [Published/Scheduled Posts 'Watching First Post' notifications not being triggered](https://meta.discourse.org/t/published-scheduled-posts-watching-first-post-notifications-not-being-triggered/273849/8):

Enabling the `disable category edit notifications` setting prevents ‘Watching/Watching First Post’ notifications from being created when a topic is manually re-categorized.

This is very useful when cleaning up old topics and prevents the [avalanche](https://meta.discourse.org/t/any-way-to-prevent-notifications-for-post-merges-moves/23796/18) of [emails](https://meta.discourse.org/t/bulk-editing-topic-categories-should-not-trigger-thousands-of-email-notifications/265269/1) that was common before this setting was implemented.

However, after a recent change in beta8, having that setting enabled now means that publishing (re-categorizing) a topic with a timer will not trigger any notifications to people who are watching that category.

It would be good to separate those two behaviors when the `disable category/tag edit notifications` setting is enabled:

- changing category/tag **manually doesn’t trigger notifications**
- changing category/tag **with a timer does trigger notifications**

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [4 augustus 2023 om 10:14 UTC](https://meta.discourse.org/t/trigger-notifications-on-scheduled-category-change-but-not-on-manual-ones/273931/2 "2023-08-04T10:14:18Z")

</div>

> [@Nacho\_Caballero](#):
>
> However, after a recent change in beta8

The [change I made in beta8](https://github.com/discourse/discourse/commit/d0cbbbe7737cf647f5410d833c4e6402a41305b7) was just to clarify the description of the site settings - it didn’t actually change any behaviour. But still, I totally agree that separating out the behaviour would be great.

The other case to consider here is ‘publishing’ topics from a PM or from shared drafts. So I don’t think ‘with a timer’ is necessarily the best way to separate it 🤔

> [@Nacho\_Caballero](#):
>
> This is very useful when cleaning up old topics and prevents the [avalanche](https://meta.discourse.org/t/any-way-to-prevent-notifications-for-post-merges-moves/23796/18) of [emails](https://meta.discourse.org/t/bulk-editing-topic-categories-should-not-trigger-thousands-of-email-notifications/265269/1) that was common before this setting was implemented.

Is this kind of cleanup always done via the ‘bulk’ tools? If so… perhaps we’d be better off removing the site settings and having a checkbox available on bulk actions like “skip notifications for this category change”

---

<div class="post-metadata">

### Author: ![Nacho\_Caballero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nacho_caballero/32/130189_2.png) [@Nacho\_Caballero](https://meta.discourse.org/u/Nacho_Caballero)
#### Post date: [4 augustus 2023 om 10:32 UTC](https://meta.discourse.org/t/trigger-notifications-on-scheduled-category-change-but-not-on-manual-ones/273931/3 "2023-08-04T10:32:25Z")

</div>

> [@david](#):
>
> it didn’t actually change any behaviour

It might have been a later change. All I know is that notifications were being generated on July 31 but not on August 1.

> [@david](#):
>
> The other case to consider here is ‘publishing’ topics from a PM or from shared drafts. So I don’t think ‘with a timer’ is necessarily the best way to separate it

Agreed. 👍

> [@david](#):
>
> Is this kind of cleanup always done via the ‘bulk’ tools? If so… perhaps we’d be better off removing the site settings and having a checkbox available on bulk actions like “skip notifications for this category change”

I think that’s the direction that’s being explored:

> [@Bulk editing topic categories should not trigger thousands of email notifications](https://meta.discourse.org/t/bulk-editing-topic-categories-should-not-trigger-thousands-of-email-notifications/265269/6):
>
> You are about to change categories on 1293 topics which will notify 8000 people watching the #new::tag category, Would you like to notify them?
