We recently changed the way the status of past executions is determined and hit a few bumps along the way. Bug fixes are available by now but would only affect new executions. Seeing your executions seems to be dated February and earlier from looking at the screenshot, perhaps you can simply delete them directly from your database’s execution_entity table to avoid any confusion about their status? Make sure to take a backup beforehand, just in case.
If this is still happening for new executions please do let us know.
Hi @Mikhail - there’s numerous ways to access your database, but an easy one would be using some free software like Beekeeper Studio to connect to your database with a nice, simple interface. I’m only suggesting it as it’s what I use!
Just ensure your settings are correct as per any credentials you’ve set in your Docker environment / Docker compose file after selecting the correct database type, and you should be good to go!