# Delete replies (or have the option to do so) when using Schedule Publish via a topic timer **URL:** \ **Category:** Feature\ **Tags:** topic-timers\ **Created:** [July 25, 2023, 2:59pm UTC](https://meta.discourse.org/t/delete-replies-or-have-the-option-to-do-so-when-using-schedule-publish-via-a-topic-timer/272778 "2023-07-25T14:59:04Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![mattdm](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mattdm/32/216484_2.png) [@mattdm](https://meta.discourse.org/u/mattdm)\ **Post date:** [July 25, 2023, 2:59pm UTC](https://meta.discourse.org/t/delete-replies-or-have-the-option-to-do-so-when-using-schedule-publish-via-a-topic-timer/272778/1 "2023-07-25T14:59:05Z")
Continuing the discussion from [Use a Topic Timer to schedule a topic to be published in the future](https://meta.discourse.org/t/use-a-topic-timer-to-schedule-a-topic-to-be-published-in-the-future/60731/69): I’m putting this in its own topic so it doesn’t\[1\] get deleted by the topic timer on that topic. As an organizer in a community which uses Discourse for communications, I would like to have private conversations about a scheduled topic, and not worry about those comments being published. Usually, such comments are trivial — suggestions, corrections, etc., not really sensitive. They aren’t really worth preserving, either. One can remember to delete all of these before scheduling the topic, but that’s easy to forget, and there is (by definition) a window between topic’s scheduling and its publication, where new replies could come in and be forgotten. Another possible solution, focusing on that last-mentioned problem: once a post is scheduled, do not allow more replies. * * * 1. with some of whatever kind of irony this kind of irony is, given the request --- _[View the full topic](https://meta.discourse.org/t/delete-replies-or-have-the-option-to-do-so-when-using-schedule-publish-via-a-topic-timer/272778)._