I logged a Jira bug for this issue, to which the Opera Aria QA Team replied on April 25th PT with the following:
Dear User,
We are aware of this issue. Currently we are working to solve this problem. As a walk around you can try to quit >ollama.exe process. This should solve your problem for a while.
Bests regards,
Opera Aria QA Team
So it seems they are at least aware and working on fixing the issue.
The suggested workaround of exiting the ollama process didn't change anything for me, but I'm using a Mac while the workaround read as Windows-oriented.