It should be fixed in the next update, but there is no ETA for that yet.
EDIT: a fix for existing saves was made a week ago, so I removed the 'hopefully' from the reply above, and the comment that a couple of the programmers were discussing the case for existing saves.
In our save, the bug is stil here... :-( Nothing has changed. Our version is v2.0.104.737