This is a known issue since the last update. A fix is included in Early Access testing, so it should get fixed for everyone in the next production update in a week or two.
@Suedkiez is 100% correct! We have a fix that should be pushed to our next Production update within the next week or so - thank you for your patience in the meantime!