I could reproduce the described behavior on the exact version you’ve provided.
I then double tabbed and upgraded to 5.0.2-1635960608.907062b7.buster which, at least on my machine™ does fix the issue.
We’ve been working hard and steady on fine tuning some things.
I’m sure this is indirectly caused by the way Core Workflow functions.
Yes, the update to 5.0.2-1635960608.907062b7 solves the issue!
FYI: The last version I had installed was 5.0.2-1635862975.49759f0b, which still caused the problem.