So I followed your instructions in a fresh testing repo and it worked as expected (over-due schedules being detected as misfires).
After a while (way too long...) of being perplexed why our own JSReports repo was not detecting misfires, I wondered if Docker was somehow caching the modules. I did a
docker-compose down command, and afterwards over-due schedules were detected as misfires.
Side note - the logs showed:
info: Using extension scheduling@github:jsreport/jsreport-scheduling#0a6b8c39577c829b525a82078691d4f100426ee5
when that extension seemed to not actually be used, which was confusing.
Thanks for your help,
Info about docker setup, for reference/posterity.
#Override file will run by default if not excluded or -f is not included at local runtime. This is standard docker-compose behavior
#for local branch, docker compose will look different, attaching the local volume: Want to keep the file system files updated for version control.