# Designer showing concurrent user (me)

**URL:** <https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225>\
**Category:** Ignition\
**Tags:** designer\
**Created:** [February 5, 2024, 1:51pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225 "2024-02-05T13:51:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\
**Post date:** [February 5, 2024, 1:51pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/1 "2024-02-05T13:51:38Z")

</div>

Per the title, the designer is showing that I have a concurrent session, but the Gateway only shows my 1 designer session. I have closed and reopened the designer. The IP address it shows for the other session is not my current IP address. How can I end that session, so I don't get warnings on editing?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fab84e4985f806138bb1983b14b2af3fd0950fb5.png)

Thanks!

---

<div class="post-metadata">

**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\
**Post date:** [April 23, 2024, 5:57pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/2 "2024-04-23T17:57:15Z")

</div>

I am also having this issue. However, the IP address shown _is_ correct. I have exited, exited & saved, etc. the Designer multiple times, but it still shows me as a 2nd concurrent user.

Did you ever resolve yours and, if so, how?

---

<div class="post-metadata">

**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\
**Post date:** [April 23, 2024, 6:08pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/3 "2024-04-23T18:08:52Z")

</div>

A gateway restart resolved the issue. I'm not aware of anything less intrusive than that.

---

<div class="post-metadata">

**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\
**Post date:** [April 23, 2024, 6:11pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/4 "2024-04-23T18:11:18Z")

</div>

Thanks

---

<div class="post-metadata">

**Author:** ![Italo\_Saavedra](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/italo_saavedra/32/36627_2.png) [@Italo\_Saavedra](https://forum.inductiveautomation.com/u/Italo_Saavedra)\
**Post date:** [July 30, 2024, 12:32pm UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/5 "2024-07-30T12:32:10Z")

</div>

Hello everybody, Does somebody know how reset "concurrent users" no gateway restarting?

Thanks

---

<div class="post-metadata">

**Author:** ![Syed\_Najam\_ul\_arfeen](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Syed\_Najam\_ul\_arfeen](https://forum.inductiveautomation.com/u/Syed_Najam_ul_arfeen)\
**Post date:** [February 19, 2026, 4:34am UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/7 "2026-02-19T04:34:04Z")

</div>

Has anyone resolved the concurrent users issue without restarting the gateway? (2)

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [March 1, 2026, 12:46am UTC](https://forum.inductiveautomation.com/t/designer-showing-concurrent-user-me/85225/8 "2026-03-01T00:46:37Z")

</div>

> [@Syed\_Najam\_ul\_arfeen](#):
>
> Has anyone resolved

Nope. Other than simply ignoring it, this is still the only way I've found to resolve the issue. Fortunately, it doesn't seem to happen very often, and aside from a few repetitive warnings, I don't believe this problem inhibits project work in any real way.
