A retry is not a bill.

Video caption

A retry is not a bill.

Repeated steps may appear in the meter.

Application progress, allocated time, and adjusted invoice.

The charge belongs beside the completed result.

#EricFieldNotes

Full written post / accessibility read

In a fictional spot fine-tune, one allocation is reclaimed and a second finishes the job. The usage chart can show both attempts. What the customer owes depends on exclusions, credits, rates, and the contract. Do not price the run from the retry badge.

Picture ninety percent of training steps done before reclaim. The usable checkpoint is older, so the replacement repeats work. A GPU utilization chart can describe activity while hiding which steps advanced the model and which charges survived adjustments.

Keep the checkpoint and accepted-step trace; the scheduler's allocation timeline; and the bill's measured, excluded, credited, and net amounts. Reconcile them under the actual agreement. If the IDs do not join, the buyer cannot explain cost per finished run.

Demand a per-run receipt that reconciles progress with net billed usage. Do this because a spot discount matters only after repeated compute, exclusions, and credits are accounted for against the result the customer received.

#EricFieldNotes

Four-beat scene transcript

1. A retry is not a bill.

In a fictional spot fine-tune, one allocation is reclaimed and a second finishes the job. The usage chart can show both attempts. What the customer owes depends on exclusions, credits, rates, and the contract. Do not price the run from the retry badge.

Visual: Measured GPU usage and net charges are different receipts.

2. The job finished; the accounting did not.

Picture ninety percent of training steps done before reclaim. The usable checkpoint is older, so the replacement repeats work. A GPU utilization chart can describe activity while hiding which steps advanced the model and which charges survived adjustments.

Visual: Repeated steps may appear in the meter.

3. Join three receipts by run ID.

Keep the checkpoint and accepted-step trace; the scheduler's allocation timeline; and the bill's measured, excluded, credited, and net amounts. Reconcile them under the actual agreement. If the IDs do not join, the buyer cannot explain cost per finished run.

Visual: Application progress, allocated time, and adjusted invoice.

4. Price accepted work, not retry events.

Demand a per-run receipt that reconciles progress with net billed usage. Do this because a spot discount matters only after repeated compute, exclusions, and credits are accounted for against the result the customer received.

Visual: The charge belongs beside the completed result.

Research and claim limits

• CoreWeave Spot Node Pools documentation (S178)
• CoreWeave Slurm Job Metrics (S179)
• CoreWeave Usage by product and zone documentation (S180)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.