# 'com.inductiveautomation.perspective.gateway.script' object has no attribute 'active\_call' **URL:** \ **Category:** Ignition\ **Tags:** perspective, scripting\ **Created:** [July 11, 2023, 3:21pm UTC](https://forum.inductiveautomation.com/t/com-inductiveautomation-perspective-gateway-script-object-has-no-attribute-active-call/76198 "2023-07-11T15:21:32Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [July 11, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/com-inductiveautomation-perspective-gateway-script-object-has-no-attribute-active-call/76198/5 "2023-07-11T17:22:13Z")
might also be another gotcha from this: ```auto calls = self.custom.active_calls ``` @pbg See this thread: > [@\[IGN-1660\]PSA - Assigning values to a property in a script may drive you nuts](https://forum.inductiveautomation.com/t/ign-1660-psa-assigning-values-to-a-property-in-a-script-may-drive-you-nuts/76192/4): > > Among other things, basically, don't do this. You're capturing the 'property tree' wrapper housed at self.custom.data in your script. Mutations are primarily forwarded to the actual backing store (because that's what matters, and what syncs to the frontend) and there's a longstanding bug where the local instance you have doesn't reflect those updates correctly. It's mostly been a nuisance bug because the typical pattern (referring to component props fully qualified all the time) avoids it. --- _[View the full topic](https://forum.inductiveautomation.com/t/com-inductiveautomation-perspective-gateway-script-object-has-no-attribute-active-call/76198)._