# Empty Workflows should not be saved

**URL:** https://meta.discourse.org/t/empty-workflows-should-not-be-saved/410997
**Category:** UX
**Tags:** workflows
**Created:** [August 26, 2026, 5:43pm UTC](https://meta.discourse.org/t/empty-workflows-should-not-be-saved/410997 "2026-08-26T17:43:48Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [August 26, 2026, 5:43pm UTC](https://meta.discourse.org/t/empty-workflows-should-not-be-saved/410997/1 "2026-08-26T17:43:48Z")

</div>

When creating a new workflow, the current behavior saves it immediately, and then admins need to remove them if they just did not actually create it.

A simple filter that only saves when there was at least one change in the default template could handle this minor detail and prevent the extra delete step.

---

_[View the full topic](https://meta.discourse.org/t/empty-workflows-should-not-be-saved/410997)._