# Weweb 3.0 "On Mounted" Element Event Trigger Removed

**URL:** <https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605>\
**Category:** Ask us anything\
**Created:** [February 18, 2025, 2:29am UTC](https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605 "2025-02-18T02:29:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AgentD](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agentd/32/6331_2.png) [@AgentD](https://community.weweb.io/u/AgentD)\
**Post date:** [February 18, 2025, 2:29am UTC](https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605/1 "2025-02-18T02:29:55Z")

</div>

Hi @Raphael and @Alexis and @luka and @ishika and @joyce.

There is an ISSUE I am facing.

The Weweb 3.0 the workflow trigger called “On Mounted” is missing

So here is the situation. Before, in Weweb 2.0 there used to be a workflow trigger called “On Mounted” for every single element, which fired when the element was added to the DOM and was useful for performing element side-effects. Now, it is no longer there.

I have CRITICAL project flows that rely on that and I can see it was removed from the editor, but the underlying code still exists cos it’s not breaking in my production apps it just precludes new use.

Please can it be returned? Thanks a lot ❤

---

<div class="post-metadata">

**Author:** ![flo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/flo/32/13260_2.png) [@flo](https://community.weweb.io/u/flo)\
**Post date:** [February 18, 2025, 2:36pm UTC](https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605/2 "2025-02-18T14:36:54Z")

</div>

Hi @AgentD,

Thank you for your kind words. We didn’t plan to remove this trigger, so I completely understand your frustration if it’s missing on your end.

I can still see it on my side, so I’ll need more details to understand what’s happening with your project. Could you reach out to the support team here 👇, and tell them on which element you have this issue? I’ll make sure they prioritize your request so we can investigate.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/3/3e654c0cf5da4ff20924f12e3bb4df78ad2650ba.png)

---

<div class="post-metadata">

**Author:** ![flo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/flo/32/13260_2.png) [@flo](https://community.weweb.io/u/flo)\
**Post date:** [February 18, 2025, 2:48pm UTC](https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605/3 "2025-02-18T14:48:35Z")

</div>

I just checked with the support team, and it was fixed an hour ago. Can you confirm if everything is back to normal on your end?  
That’s why I could not reproduce on my side.

I’m really sorry for the inconvenience.

---

<div class="post-metadata">

**Author:** ![AgentD](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agentd/32/6331_2.png) [@AgentD](https://community.weweb.io/u/AgentD)\
**Post date:** [February 20, 2025, 6:17pm UTC](https://community.weweb.io/t/weweb-3-0-on-mounted-element-event-trigger-removed/16605/4 "2025-02-20T18:17:52Z")

</div>

Thanks a lot @flo it’s all up and running again. Super grateful for you guys.