Christopher Schleiden

We could extend this to look at all HTML fields on `Details`...

Your solution is correct, I think that's a bug in the code determining whether the solution is correct or now. There have been some issues with the last few lessons.

Added the latest batch of bugs and partially implemented features I'd like to fix and finish before releasing 1.0.

With #245 this should be easier to implement.

Instead of the moving `v1` tag, use a specific one like 1.2 or 1.3

This is fixed by https://github.com/cschleiden/go-workflows/pull/316 for the `redis` backend

`WorkflowTaskStarted` is added for every "execution slice", that wouldn't be the correct event to check here. I think the UI needs to be upated to handle this error scenario 🤔

🤔 wouldn't that run the `(.+?)` regex which would match the whole input?

Are you using a self-hosted or hosted runner? `node16` should be supported in the current versions of the runner: https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions

It's a good suggestion but unfortunately VSTS does not provide that extension at the moment.