# Pre-save functionality with respect to save and extensions on pre-save

**URL:** https://community.nextw.com/t/pre-save-functionality-with-respect-to-save-and-extensions-on-pre-save/933
**Category:** Nextworld Platform
**Created:** [July 31, 2025, 8:51pm UTC](https://community.nextw.com/t/pre-save-functionality-with-respect-to-save-and-extensions-on-pre-save/933 "2025-07-31T20:51:42Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ellen.kaufman](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ellen.kaufman/32/396_2.png) [@ellen.kaufman](https://community.nextw.com/u/ellen.kaufman)
#### Post date: [July 31, 2025, 8:51pm UTC](https://community.nextw.com/t/pre-save-functionality-with-respect-to-save-and-extensions-on-pre-save/933/1 "2025-07-31T20:51:42Z")

</div>

Hello! Do we expect the logic/updates that happens on a LB configured on a presave of an application to also roll back what happens on the save of an application if there is an error in the presave logic or extensions of the presave logic?

---

<div class="post-metadata">

### Author: ![joeyates23](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/joeyates23/32/202_2.png) [@joeyates23](https://community.nextw.com/u/joeyates23)
#### Post date: [July 31, 2025, 9:00pm UTC](https://community.nextw.com/t/pre-save-functionality-with-respect-to-save-and-extensions-on-pre-save/933/2 "2025-07-31T21:00:20Z")

</div>

That is correct. Whenever a logic block errors, then changes from that logic block in that container should be rolled back.

---

<div class="post-metadata">

### Author: ![Aaron.C](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/aaron.c/32/163_2.png) [@Aaron.C](https://community.nextw.com/u/Aaron.C)
#### Post date: [July 31, 2025, 10:40pm UTC](https://community.nextw.com/t/pre-save-functionality-with-respect-to-save-and-extensions-on-pre-save/933/3 "2025-07-31T22:40:28Z")

</div>

A note that pre-save is an application event in contrast to a pre-insert table trigger. There are other differences in UX when it comes to other message types such as WARNINGS or INFO. But both would act the same as @joeyates23 noted and roll back whatever transactions have occurred in that call stack transaction in an error scenario. A note, if multiple transaction boundaries exist in the stack. The error may not roll back all changes. Proper error handling is important when dealing with multiple transactions in the same call stack