After deploying an updated sequence file to a production test station, technicians report that the new limits are not being applied. The old sequence appears to still be running. What is the most likely cause?
-
A
The station cache has the old sequence locked in memory and the process must be restarted
-
B
The sequence file was deployed to the wrong directory and the station is loading from a cached path
-
C
The TestStand Runtime License does not support sequence updates
-
D
The operator interface does not support hot-swapping sequence files