# Using system.db.refresh() to update connection to a global script **URL:** \ **Category:** Ignition\ **Created:** [October 4, 2023, 4:33pm UTC](https://forum.inductiveautomation.com/t/using-system-db-refresh-to-update-connection-to-a-global-script/80026 "2023-10-04T16:33:36Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [October 4, 2023, 6:11pm UTC](https://forum.inductiveautomation.com/t/using-system-db-refresh-to-update-connection-to-a-global-script/80026/6 "2023-10-04T18:11:58Z")
When you import a project script, it'll bring a copy of the Python code into the local script _as it was at the time of import_, which can cause all kinds of fun: > [@Some Project Resources not publishing](https://forum.inductiveautomation.com/t/some-project-resources-not-publishing/16888/3): > > This may be a side-effect of the fact that Ignition doesn’t/can’t track the usage and retention of python code objects throughout the gateway. This means that when your script modules have interlocking dependencies, updating one script won’t impact the code objects that other scripts have imported. You may need to make a trivial change in all of your scripts and save them all together to get it to “take”. You may also need to disable then re-enable the entire project. Consider renaming the o… --- _[View the full topic](https://forum.inductiveautomation.com/t/using-system-db-refresh-to-update-connection-to-a-global-script/80026)._