For san francisco compute infrastructure and model engineering teams
SF Compute cancelled order or failed training worker?
Keep the pool allocation window and instance lifecycle beside application logs. A capacity order that did not fill is not evidence of a GPU runtime failure.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a resolved San Francisco Compute workflow 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
Compare the first failure, quoted evidence and unresolved questions with an incident your team has already resolved. Begin with this question: Was compute time allocated to the pool? Only attribute a process, rank, device or recovery state when the submitted evidence establishes it.
Was compute time allocated to the pool?
Evidence to compare: Order state, allocation window and the instance start event.
An unavailable allocation explains why no process could run. Separate that control-plane question from the later worker timeline.
Did the worker stop within its intended window?
Evidence to compare: Instance lifecycle, allocation timing and the first application exception.
A scheduled boundary and an application defect can both end work. Preserve the timing and actual termination reason instead of guessing from a client disconnect.
Can the next attempt recover progress?
Evidence to compare: Checkpoint completion and the artifact selected by the new application attempt.
A new allocation does not certify a recovery file. Verify the application state independently before proposing a continuation.
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
