We had an issue a couple weeks ago where a SQL query tag was accidentally set to a scan class that didn’t exist, due to a typo. When this happens on a regular tag (not a UDT), Ignition will create a scan class for you (without any message popup) with a scan rate of 1,000 ms. We’ve confirmed this with support, although it seems like it was not 100% intentional design.
My question is, Is there any way to get into the install files/config and change the default scan class to be something like 10 or even 30 seconds to guard against this in the future? We had a catastrophic failure of our gateway and the system was down for over 24 hours as it was being rebuilt due to this.
I’ve already confirmed that simply changing the scan classed named ‘Default’ does nothing about the scan classes auto-created.