# On\_change\_notify issue

**URL:** https://discuss.tryton.org/t/on-change-notify-issue/9311
**Category:** Developer
**Tags:** sales
**Created:** [August 7, 2026, 8:47pm UTC](https://discuss.tryton.org/t/on-change-notify-issue/9311 "2026-08-07T20:47:32Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![eva\_luadora](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/eva_luadora/32/3903_2.png) [@eva\_luadora](https://discuss.tryton.org/u/eva_luadora)
#### Post date: [August 10, 2026, 8:52am UTC](https://discuss.tryton.org/t/on-change-notify-issue/9311/2 "2026-08-10T08:52:17Z")

</div>

Hi Jakob,

I think the `warning` type is fine.

In Sao, each `on_change_notify` result refreshes the notification area before displaying the returned messages. If another `on_change_notify` call occurs immediately afterwards and returns an empty list, the previous warning will briefly appear and then disappear.

I would check the browser Network tab to see whether `on_change_notify` is called more than once when changing `party`, and what each response contains.

Also ensure that `fields.depends` includes every field used to compute the warning, especially fields modified by `on_change_party()`. Otherwise a subsequent onchange may evaluate the condition with different values and return no notification.

If you can share the complete method and domain, it should be easier to identify which dependency or onchange causes the second result.

---

_[View the full topic](https://discuss.tryton.org/t/on-change-notify-issue/9311)._