Groov- value has not been received yet

groov View
1

I get the following message every once in a while when first loading a page in groov:

Groov no value
Groov no value.png757×256 14 KB

It seems to imply that groov is going to try again, but the yellow triangles stick around until I refresh the page. Notice that some of the values are working - these happen to be IO points and the ones with the triangles are strategy variables, but at other times it is a random mix.

Nothing unusual in the logs at that time:

Log Summary 
2018-03-28, 11:59:33 GMT-07:00 INFO com.allen_sauer.gwt.log.client.Log - first value timeout called
2018-03-28, 11:59:33 GMT-07:00 INFO com.allen_sauer.gwt.log.client.Log - first value timeout called
2018-03-28, 11:59:23 GMT-07:00 INFO com.opto22.groov.server.data.SubscriptionManager - rebuildScannerSubscriptions - Scanning 61 tags in 4 scanner subscriptions.
2018-03-28, 11:59:22 GMT-07:00 INFO com.opto22.groov.server.data.SubscriptionManager - cleanupSubscriptions - Removed 1 client subscriptions.
2018-03-28, 11:59:22 GMT-07:00 INFO com.opto22.groov.server.data.SubscriptionManager - rebuildScannerSubscriptions - Scanning 94 tags in 5 scanner subscriptions.
2018-03-28, 11:59:21 GMT-07:00 INFO com.opto22.groov.server.rpc.ClientServiceImpl - User 'philip' is viewing page 'Configuration'.
2018-03-28, 11:44:23 GMT-07:00 INFO com.opto22.groov.server.data.SubscriptionManager - rebuildScannerSubscriptions - Scanning 61 tags in 4 scanner subscriptions.
2018-03-28, 11:44:22 GMT-07:00 INFO com.opto22.groov.server.data.SubscriptionManager - cleanupSubscriptions - Removed 1 client subscriptions.
2018-03-28, 11:44:08 GMT-07:00 INFO com.allen_sauer.gwt.log.client.Log - first value timeout called
2018-03-28, 11:44:08 GMT-07:00 INFO com.allen_sauer.gwt.log.client.Log - first value timeout called
2

Can you try switching to a different page and back with it refreshing the browser and see if that makes a difference?

I retooled the tag scanning code pretty heavily in this release to try and make sure we’re not scanning anything more than necessary, and I’ve run into a couple cases where it’s a bit overzealous in pruning tags. I thought I caught them all before release, but probably not.

3

Yes, switching to a different page and back works.