Hi @NdnaJnz - there is a known fix; the bug is due to erroneous data in your sites.json file. You can follow along in this thread on how to fix it. It involves opening that file, and deleting the “status: running” line for the sites affected.
I’m going to merge this to a bigger bugs post and I’ve created a ticket for the engineering team to look in to.