# Trigger event on View startup/refresh/etc

**URL:** <https://forum.inductiveautomation.com/t/trigger-event-on-view-startup-refresh-etc/91264>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 3, 2024, 7:21am UTC](https://forum.inductiveautomation.com/t/trigger-event-on-view-startup-refresh-etc/91264 "2024-06-03T07:21:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [June 3, 2024, 7:21am UTC](https://forum.inductiveautomation.com/t/trigger-event-on-view-startup-refresh-etc/91264/1 "2024-06-03T07:21:41Z")

</div>

I'm struggling to fire an event off every time a dock loads, whether it's by browser page refresh, project update which reloads the page, initial session launch, or loads of a page after visiting another url and you come back.

Currently, I can get it to fire on project update reload (project update notification shows and push reload) and on initial session launch, but I can't get it to work for browser page refreshes and url navigations to and from (e.g. navigate to Perspective client url, then navigate to google, then back to Perspective, in this case the even will only trigger on the first nav to Perspective, not the second as well).

I can't figure out how I can trigger on these events... I only want it to trigger on loading/reloading of the dock, not of a main view.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 3, 2024, 11:55am UTC](https://forum.inductiveautomation.com/t/trigger-event-on-view-startup-refresh-etc/91264/2 "2024-06-03T11:55:51Z")

</div>

It's the same with page reloads for main views. There simply is no event for that. There is no way to distinguish such deliberate reloads from brief connection break/restore events, and having the latter cause side effects would be disastrous.
