Release Notes can be found here.
Error message: Lock wait timeout exceeded
Some of my workflows have been failing with the following error message this afternoon:
I'm happy to restart them to see if they'll just work on a second attempt, but some of the workflows are still running, but look like they might be in a confused state. There are tasks that have stderr that look like they should have been completed, but still say "running" and at least one said "Queued in Cromwell". I'm going to restart the whole set now, but wondered if others were seeing weird behavior.