# Multiple Tab Issue\_ **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [September 21, 2025, 2:43am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810 "2025-09-21T02:43:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![boopathig502](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/boopathig502/32/79853_2.png) [@boopathig502](https://forum.inductiveautomation.com/u/boopathig502)\ **Post date:** [September 21, 2025, 2:43am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/1 "2025-09-21T02:43:47Z")
We developed one Perspective project. The project scripts run in both component and gateway scope. Sometimes, we face issues where the scripts do not run properly because the operator either closes the project while it is running, or opens the project in multiple tabs. How can I prevent this issue? Currently, when the project is logged in, we write **TRUE** to a tag, and when the operator logs out, we write **FALSE** to that tag. If the tag is **FALSE** , then login is allowed; otherwise, it is not. The problem is that sometimes the operator does not log out and simply closes the Edge browser. We tried writing a shutdown script, but it is not working. How can we solve this problem??? ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 21, 2025, 2:57am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/2 "2025-09-21T02:57:21Z")
Ignition is intended to allow multiple logins. Is there any valid reason for only allowing 1 user at a time? Usually you should make your program work with any number of users logged in at any time. ---
**Author:** ![boopathig502](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/boopathig502/32/79853_2.png) [@boopathig502](https://forum.inductiveautomation.com/u/boopathig502)\ **Post date:** [September 21, 2025, 3:04am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/3 "2025-09-21T03:04:57Z")
If multiple users are allowed to log in, then the script does not run properly, because we are getting values from OPC tags and the script runs on **valueChanged**. If multiple tabs are opened, then the script runs two or more times. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [September 21, 2025, 4:24am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/4 "2025-09-21T04:24:19Z")
This sounds like this should be a gateway tag changed script, not a session based script. Maybe share your script, how it is supposed to work and where it’s located and we will be able to engineer around the issue with you? ---
**Author:** ![Cose\_Peter1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cose_peter1/32/79174_2.png) [@Cose\_Peter1](https://forum.inductiveautomation.com/u/Cose_Peter1)\ **Post date:** [September 21, 2025, 6:11am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/5 "2025-09-21T06:11:34Z")
Why do you have to write True and False to a tag when operator logs in and out? Why not use the session property `self.session.props.auth.authenticated` to check if operator is logged in or not? ---
**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\ **Post date:** [September 21, 2025, 6:51am UTC](https://forum.inductiveautomation.com/t/multiple-tab-issue/110810/6 "2025-09-21T06:51:51Z")
Sounds like an xy problem. Tell us what your end goal is and we’ll help you figure out a better way to do it, instead of working around a broken methodology.