# Perspective Page Refresh

**URL:** <https://forum.inductiveautomation.com/t/perspective-page-refresh/103341>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 6, 2025, 5:24pm UTC](https://forum.inductiveautomation.com/t/perspective-page-refresh/103341 "2025-03-06T17:24:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MG3](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mg3/32/84125_2.png) [@MG3](https://forum.inductiveautomation.com/u/MG3)\
**Post date:** [March 6, 2025, 5:24pm UTC](https://forum.inductiveautomation.com/t/perspective-page-refresh/103341/1 "2025-03-06T17:24:04Z")

</div>

Hi all,

Is there a way to detect a manual page refresh (F5) in perspective? I've tried the `onStartup()` system event but from what I can tell this is only trigged when the project is started or an update has been sent, etc.

I did reference this past forum post: [Perspective script/action on page refresh or view save - #2 by mcarritt1](https://forum.inductiveautomation.com/t/perspective-script-action-on-page-refresh-or-view-save/39171/2) in which a user appears to get what they need working with the `onStartup()` system event on their components but this doesn't seem to work for me either (I have tested `onStartup()` on both my view and my components using `system.perspective.print()`).

Any work arounds or anything I am missing here? This issue is causing me a real headache! Any help is appreciated, thanks for reading!

MG3

---

<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:** [March 6, 2025, 5:31pm UTC](https://forum.inductiveautomation.com/t/perspective-page-refresh/103341/2 "2025-03-06T17:31:39Z")

</div>

No. The gateway cannot distinguish deliberate page reload from accidental reload due to communication hiccups. Neither HTTP nor websocket technology can do this. IA has deliberately chosen to "ride through" possible disconnect/reconnect events.
