# Order of startup **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [December 12, 2024, 6:07am UTC](https://forum.inductiveautomation.com/t/order-of-startup/99732 "2024-12-12T06:07:25Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 12, 2024, 1:23pm UTC](https://forum.inductiveautomation.com/t/order-of-startup/99732/2 "2024-12-12T13:23:10Z")
No documentation of order. Tags start up in parallel with everything else. Avoid reading tags or doing any network callouts in the top level of project scripts anyways: > [@\[IGN-6503\]Project Library Script Initialization Races](https://forum.inductiveautomation.com/t/ign-6503-project-library-script-initialization-races/98636): > > Are you annoyed by pseudo-random breakage in Ignition project library scripting? Odd top-level constants being garbled, or operations in the top level that have side effects running twice? Or more? Not happening much, but always around project edits, and sometimes even on gateway restart? Yeah, me too. frowning_face Poking around under the hood back in the spring, for a module development task, I ran across some problematic IA bytecode and pinged some people. But it went nowhere, as I co… I would expect tags to be initialized **after** scripting anyways, because they generate script operations. --- _[View the full topic](https://forum.inductiveautomation.com/t/order-of-startup/99732)._