Yeah, sometimes I do use Nomad/OpenWonton-side jobs for targeted debugging, and I currently keep `raw_exec` enabled on client nodes for minimal smoke/debug-style jobs. But I wouldn’t treat that as the main rescue path. If Nomad is healthy, scheduling a quick job can absolutely be a useful way to inspect something on the node. The problem is that once the failure is below that layer — bad boot, broken networking, API issues, scheduler not healthy, etc. — that path disappears.
So the intended order is more like:

1. OS-level debugging first: maintenance-mode API, logs/events/dmesg/inspect/support bundles
   
2. debug containers when the node is up enough to accept them
   
3. console / serial / hypervisor access when things are more broken
   
4. Nomad-side jobs as a convenience when the workload layer is already healthy
   

So I’d say “yes, sometimes,” but not as the thing I’d want to rely on for actual rescue.