Got a hint from another thread (thanks @twhitehouse) that this could be caused by spec failing. Found this while tailing ~/.nvwb/logs/workbench.log
{"level":"error","error":"Problem validating new project:\ninvalid application (idx 0): invalid application (no health check command set)\ninvalid application (idx 0): invalid application (no stop command set)","projectPath":"/home/nvwb/nvidia-workbench/brainwavecollective-nvwb-tl-jockey","time":"2024-10-02T05:00:01Z","message":"Project spec validation failed."}
{"level":"warn","runtimeInfoPath":"/home/nvwb/.nvwb/project-runtime-info/brainwavecollective-nvwb-tl-jockey-b27f43bd8e4c26bac86d1ab008f5d0d6f5efacdb","time":"2024-10-02T05:00:01Z","message":"No git remote operation output files were found."}
I removed the problematic entry (which was from a recent commit) and we’re back in business.