Comms established, binding on screen still broken?

So we are seeing something that is a little strange. We built our screens and linked properties like background color to the appropriate tag name via bindings. Today, we got our first station talking, and the driver is corretly polling the data, which is displaying in our tag browser. For example, generator run status is a boolean “0” in the tag database. But, the property of the component that it is linked to still shows a “Bad_NotFound” for the tag. We find that manually re-linking the tag does fix the problem, but this isn’t ideal. Any ideas?