For high-performance computing and distributed training leads
Pinpoint which straggler rank or RoCE link slowed down your Crusoe Cloud cluster.
Compare per-rank step completion drift, shared storage checkpoint durations, and RDMA pause frames before a slow worker trips the global NCCL watchdog.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a resolved Crusoe Cloud Slurm straggler incident
Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.
Before uploading, review cloud data handling and local options.
Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.
Try Denpex for 30 days. FREE.
No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.
Start your free 30-day Team evaluation
Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.
What a useful evaluation should establish
Establish whether a timeout was caused by a straggler compute node, storage write barrier, or network pause frame congestion.
Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.
Inside Denpex
See the evidence, not just the claim
Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.
Follow the failure through the cascade

Prepare the hardware escalation

Ask for the evidence that is missing

Keep the investigation in the editor

Crusoe Cloud - Observed Runtime Evidence
Incident pattern summary
A 16-node Slurm job on Crusoe Cloud times out during model checkpointing at step 5,000. Rank 0 through 119 wait at a broadcast barrier while Rank 120 stalls writing shard state to a congested mount point, causing the 10-minute NCCL watchdog to abort the entire run.
slurmstepd: error: *** STEP 48192.0 ON crusoe-h100-015 CANCELLED AT 2026-10-21T09:14:22 ***
[E ProcessGroupNCCL.cpp:915] [Rank 0] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=5001, OpType=BROADCAST, Timeout(ms)=600000)
[Rank 120] Checkpoint save to /mnt/shared/checkpoints/step_5000_shard_15.pt took 642.4s (expected < 30.0s)Recommended verification flags
Set these environment flags in your training container or launch script to capture high-resolution collective logs:
NCCL_DEBUG=INFOTORCH_NCCL_ENABLE_MONITORING=1TORCH_NCCL_HEARTBEAT_TIMEOUT_SEC=600Diagnostic Scope Boundary
Denpex cannot tune Crusoe Cloud storage throughput tiers or modify Slurm scheduler partitions. The evaluation isolates whether the stall originated in collective networking, GPU compute throttling, or storage I/O.
Other GPU Cloud Failure Workflows
Compare evidence patterns across multi-node fabrics, Kubernetes pods, and bare-metal environments.