What is your typical way of licensing your installation? (I suppose it is a standard Studio/Robot/Assistant as installed via the EXE installer).
If you license via Orchestrator connection, could it be that it looses connectivity at some point which would then indeed trigger such issue.
I suppose one way to prevent it would be to license Studio using the local licensing option under More Options. This would allow you to “fall back” to this method and in theory prevent this message from occurring.