# Error Message: Tried to register a path/listener combination that is already in the model **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [January 18, 2021, 5:50pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366 "2021-01-18T17:50:16Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![richard1](https://avatars.discourse-cdn.com/v4/letter/r/50afbb/32.png) [@richard1](https://forum.inductiveautomation.com/u/richard1)\ **Post date:** [January 18, 2021, 5:50pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/1 "2021-01-18T17:50:16Z")
I get hundreds of these error messages after starting up. What does it mean? Error is: "Tried to register a path/listener combination that is already in the model. Value: TagSubscription(path=[default]TD23, listener=com.inductiveautomation.perspective.gateway.binding.expression.ExpressionBindingTagListener@394059fc) " ---
**Author:** ![maja](https://avatars.discourse-cdn.com/v4/letter/m/3ab097/32.png) [@maja](https://forum.inductiveautomation.com/u/maja)\ **Post date:** [June 22, 2022, 12:49pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/2 "2022-06-22T12:49:35Z")
Can somebody help with this topic? I have the same issue. On the button, mouse event I have a script. In the script, I am asking if the tag value is different from some value if yes I am writing in that tag some another value. Something like. if system.tag.read(“xx”).value!=“”: system.tag.write(“xxx”, “test”) And on this, I have an error " [Tried to register a path/listener combination that is already in the model]. What is wrong with my expression? ---
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [June 24, 2022, 11:48am UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/3 "2022-06-24T11:48:39Z")
Yes, this bug has been present for a long time now... > [@Ignition 8.0.16 - warning Tried to unregister a path/listener combination that is not present in the model](https://forum.inductiveautomation.com/t/ignition-8-0-16-warning-tried-to-unregister-a-path-listener-combination-that-is-not-present-in-the-model/40174/6): > > Hi in the gateway logs, if you hover over the magnifying glass to the right, it should tell you which project, view, component, and property that this error is coming from. I’ve seen this error occur when a expression binding references the same tag path more than once e.g. {tagA} + {tagA}. Therefore if you can restructure your expression to contain only one reference of the tag path, then the error would go away. ---
**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 24, 2022, 2:10pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/4 "2022-06-24T14:10:36Z")
Does it happen in v8.1 ? (v8.0 is end-of-life.) ---
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [June 24, 2022, 3:47pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/5 "2022-06-24T15:47:15Z")
Yes, in v8.1.15 too (perspective, not vision)… ---
**Author:** ![pascal.meulenkamp](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.meulenkamp/32/55038_2.png) [@pascal.meulenkamp](https://forum.inductiveautomation.com/u/pascal.meulenkamp)\ **Post date:** [March 3, 2023, 10:58am UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/6 "2023-03-03T10:58:46Z")
Still there in 8.1.17, I've got this on an alarm enabled binding (expression). ---
**Author:** ![Richard\_Wixson](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Richard\_Wixson](https://forum.inductiveautomation.com/u/Richard_Wixson)\ **Post date:** [May 1, 2023, 10:25pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/7 "2023-05-01T22:25:51Z")
Me too. Is this an actual bug with no fix yet or is there a workaround? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 1, 2023, 10:34pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/8 "2023-05-01T22:34:16Z")
Hmm, the only ticket I can find for this says it was fixed in 8.1.17. If that's not the case get in touch with support. ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [October 7, 2025, 5:00pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/9 "2025-10-07T17:00:01Z")
This one reared its head today. Error is tried to register a path/listener combination that is already in the model…value: Tagsubscription(path=[xxx]metals listener = ClientSession. This caused a total lockup of the client, but the weird thing is, this client doesn't access the tags in the log errors at all. A completely different application. The other odd issue, is that the client that is locked up and for which the logs relate too…its IP address is not even listed in the Gateway Clients, so I cannot terminate it from the gateway. Vision 8.1.38 ---
**Author:** ![Porter\_Ellis](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Porter\_Ellis](https://forum.inductiveautomation.com/u/Porter_Ellis)\ **Post date:** [December 9, 2025, 8:59pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/10 "2025-12-09T20:59:57Z")
Still seeing this issue in my 8.1.5 edition. Any luck on the dev side? What could be causing this? This error hit my logs a few dozen times then caused the client sessions to freeze up. ---
**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:** [December 9, 2025, 9:02pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/11 "2025-12-09T21:02:35Z")
> [@Porter\_Ellis](#): > > my 8.1.5 edition Still? That version is ancient. ---
**Author:** ![Porter\_Ellis](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Porter\_Ellis](https://forum.inductiveautomation.com/u/Porter_Ellis)\ **Post date:** [December 9, 2025, 9:14pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/12 "2025-12-09T21:14:40Z")
> [@pturmel](#): > > Still? That version is ancient. That is the most recent version that is non-8.3. How is that considered ancient? ---
**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:** [December 9, 2025, 9:16pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/13 "2025-12-09T21:16:53Z")
Ah. You must mean 8.1.50. ---
**Author:** ![Porter\_Ellis](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Porter\_Ellis](https://forum.inductiveautomation.com/u/Porter_Ellis)\ **Post date:** [December 9, 2025, 9:17pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/14 "2025-12-09T21:17:13Z")
Correct. Not 8.1.05. ---
**Author:** ![Porter\_Ellis](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Porter\_Ellis](https://forum.inductiveautomation.com/u/Porter_Ellis)\ **Post date:** [December 10, 2025, 4:17pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/15 "2025-12-10T16:17:59Z")
So with this issue being present in the newest stable version of 8.1, is there an explanation/solution? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 10, 2025, 4:24pm UTC](https://forum.inductiveautomation.com/t/error-message-tried-to-register-a-path-listener-combination-that-is-already-in-the-model/42366/16 "2025-12-10T16:24:38Z")
> [@Kevin.Herron](#): > > If that's not the case get in touch with support. Your first step should be to contact support officially, so they can get an actual bug ticket going and work with you to figure out what's going wrong. That said: > [@Porter\_Ellis](#): > > This error hit my logs a few dozen times then caused the client sessions to freeze up. This particular error is almost certainly merely _symptomatic_ of something else. What that is, I don't know, but something to do with the lifecycle management of tag subscriptions in Perspective, which is a complicated enough area that I'm sure edge cases exist. It's obviously not affecting _all_ customers, or there would be more activity in this thread, so if you contact support there's every chance they're already familiar with a likely root cause and can help you identify or fix it.