I am having the same issue on our workflows, and not only on lock/unlock actions, but also for suspend actions.
The error you have shown is exactly the same as mine, and it started to happen after the new patch. If I restart the workflow manually, it then works.
Support was unable to pinpoint the exact issue, does anyone have a solution for this?
Thanks.