Thanks for reporting!
@rodger reported this a while ago, and when I “fixed” it, I was referencing the javascript docs. I just checked the site docs, and it has the nuance that if “silent” is false, it quietly ignores isForceRunAfter.
I now set isSilent to true, so the next, next build (beta.14) should fix this issue (it won’t be fixed in the next upgrade because the bugfix needs to be in the running version before the upgrade)…