# Classes loading using script console cause isinstance to return False

**URL:** <https://forum.inductiveautomation.com/t/classes-loading-using-script-console-cause-isinstance-to-return-false/59737>\
**Category:** Ignition\
**Created:** [May 18, 2022, 4:52pm UTC](https://forum.inductiveautomation.com/t/classes-loading-using-script-console-cause-isinstance-to-return-false/59737 "2022-05-18T16:52:07Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**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:** [November 18, 2024, 12:36pm UTC](https://forum.inductiveautomation.com/t/classes-loading-using-script-console-cause-isinstance-to-return-false/59737/5 "2024-11-18T12:36:09Z")

</div>

See this topic:

> [@\[IGN-6503\]Project Library Script Initialization Races](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636/2):
>
> I should mention that the work-around shown above should NOT be placed in all of your project library scripts. It solves the multiple execution problem but at the risk of AB-BA deadlock across interdependent scripts. Some thoughts: Definitions of simple functions and simple assignments to top-level constants do not need this fix. While multiple executions will repeatedly replace top level objects, the replacements are identical to the first pass--no harm, no foul. Definitions of top-lev…

But also, the script console is wrapped internally to capture output, so runs its own script module initialization, separate from Vision.

---

_[View the full topic](https://forum.inductiveautomation.com/t/classes-loading-using-script-console-cause-isinstance-to-return-false/59737)._