My suggestion of work-around for the BUG 12-1GF25RP mentioned in the doc 535385.1

Hi All,
I ever happened to the issue - failed to read value of a LOV. From doc 535385.1, "Just after the start up of the component, while the LOV have not been yet loaded, several tasks are started simultaneously. If there are concurrent accesses to the same pick list, one is failing with the error".

I have suggestion for work-around for this issue, it is based on the reason above.

For example, when I try to get a value from LOV, in general, I use script below:

var sInvalid = TheApplication().InvokeMethod("LookupValue", "STATUS", "Invalid");

Since it's possible that LOV have not been yet loaded, could we add some checking to avoid the issue as below, my assumption is after several tries, the LOV is loaded, then the value of LOV can be read correctly.