# Deletion changes Name field?

**URL:** <https://community.fibery.io/t/deletion-changes-name-field/2465>\
**Category:** Bugs & Issues\
**Created:** [January 29, 2022, 11:00am UTC](https://community.fibery.io/t/deletion-changes-name-field/2465 "2022-01-29T11:00:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikkling](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@Mikkling](https://community.fibery.io/u/Mikkling)\
**Post date:** [January 29, 2022, 11:00am UTC](https://community.fibery.io/t/deletion-changes-name-field/2465/1 "2022-01-29T11:00:46Z")

</div>

I have an automation rule that triggers on Name change. When such an entity is DELETED, the rule triggers and then fails because the entity cannot be found. Is this really intended behavour?

I do not see a reason to change an entity’s Name field with strike-through upon deletion. So, quick fix is to not change the Name on deletion. If you really want to keep this feature, could you add a system-wide flag for deleted items, so I can filter the automation for only un-deleted entities?

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [January 29, 2022, 11:08am UTC](https://community.fibery.io/t/deletion-changes-name-field/2465/2 "2022-01-29T11:08:49Z")

</div>

Related:

> [@\[FIXED\] Automations error about self update failure](https://community.fibery.io/t/automations-error-about-self-update-failure/2463):
>
> I added a rule to the automation to update certain fields. If the self-entity is deleted before the update action is executed, an error occurs. “Set: State Updated Date” has failed with this error: “Failed to execute action “Update”: Some entities to update were not found.”. Please check out the Rule’s activity for more details. The reproduction process is as follows. Create an entity. Delete the created entity immediately. [image] It is not a bug that an error occurs. However, the use…

---

<div class="post-metadata">

**Author:** ![Mikkling](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@Mikkling](https://community.fibery.io/u/Mikkling)\
**Post date:** [January 29, 2022, 12:55pm UTC](https://community.fibery.io/t/deletion-changes-name-field/2465/3 "2022-01-29T12:55:29Z")

</div>

Ah, I see!

Perhaps a system-wide “deleted” flag is preferrable, then, so we can filter automations for entities that are not deleted.

Such a flag would also allow automations that do trigger on deletion, so one can write integrations that remove deleted entities in external apps.