Sandbox command reliability is back to normal. Voided work was never billed; re-run anything you are missing on a fresh fork.

An elevated share of commands running in rollout sandboxes is being cut short by infrastructure failures on our side. Any result marked void was not billed and was excluded from its batch - it is a gap in your data, not a wrong answer - and retrying it on a fresh fork is safe. We are investigating the cause. Nodes and jobs run on separate machines and are not affected.

Sandbox command reliability is back to normal. Voided work was never billed; re-run anything you are missing on a fresh fork.

An elevated share of commands running in rollout sandboxes is being cut short by infrastructure failures on our side. Any result marked void was not billed and was excluded from its batch - it is a gap in your data, not a wrong answer - and retrying it on a fresh fork is safe. We are investigating the cause. Nodes and jobs run on separate machines and are not affected.

Sandbox command reliability is back to normal. Voided work was never billed; re-run anything you are missing on a fresh fork.

An elevated share of commands running in rollout sandboxes is being cut short by infrastructure failures on our side. Any result marked void was not billed and was excluded from its batch - it is a gap in your data, not a wrong answer - and retrying it on a fresh fork is safe. We are investigating the cause. Nodes and jobs run on separate machines and are not affected.