Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] UltraReview timeout/crash consumed ~$37 in credits with no output returned [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54812•Fetched 2026-04-30 06:35:16
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
ethanortechoethanortecho
Participants
ethanortechoethanortecho
Timeline (top)
labeled ×2

Two consecutive UltraReview runs failed without producing any output, but both consumed credits. Total known charge: $37 (run 2). Run 1 charge unknown but non-zero.

This appears to be the same class of failure tracked in #49905 (timeout consumes quota) and #49882 (failed runs decrement free quota).

Root Cause

Two consecutive UltraReview runs failed without producing any output, but both consumed credits. Total known charge: $37 (run 2). Run 1 charge unknown but non-zero.

This appears to be the same class of failure tracked in #49905 (timeout consumes quota) and #49882 (failed runs decrement free quota).

RAW_BUFFERClick to expand / collapse

Summary

Two consecutive UltraReview runs failed without producing any output, but both consumed credits. Total known charge: $37 (run 2). Run 1 charge unknown but non-zero.

This appears to be the same class of failure tracked in #49905 (timeout consumes quota) and #49882 (failed runs decrement free quota).

Environment

  • Claude Code: latest (UltraReview research preview)
  • Date: 2026-04-28
  • Account: [email protected] (Automized org)

Steps to reproduce

  1. Invoke UltraReview on a project from a Claude Code session.
  2. Observe behavior across two attempts.

Expected behavior

Either the run completes and returns findings, or it fails cleanly without consuming credits.

Actual behavior

Run 1: Crashed before doing any work. No output. Credit consumption unknown but non-zero.

Run 2: Run started successfully — could see it actively finding issues and verifying issues. Mid-way through verification, the run stopped. The parent Claude Code session reported a timeout. All in-progress findings were lost — no report, no partial output, nothing surfaced back to the user. This run consumed $37 in credits.

Impact

Roughly $37+ in credits charged with zero deliverable. Per the discussion in #49905, failed remote sessions should not decrement credits/quota.

Related

  • #49905 — ultrareview timeout shouldn't consume quota credits
  • #49882 — failed runs consuming free quota

Filing this for engineering visibility. Refund request submitted separately via support.claude.com.

extent analysis

TL;DR

The issue can be mitigated by monitoring UltraReview runs for timeouts and manually refunding credits for failed runs until a permanent fix is implemented.

Guidance

  • Review related issues #49905 and #49882 for potential workarounds or fixes, as they describe similar problems with UltraReview consuming credits on failed or timed-out runs.
  • Implement a process to track and refund credits for failed UltraReview runs to prevent unnecessary charges.
  • Consider adding a timeout handling mechanism to UltraReview to prevent credit consumption in case of failures.
  • Verify that the refund request submitted via support.claude.com is processed correctly to recover the lost credits.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The provided information suggests that this issue is related to a known problem with UltraReview, and a fix might be in progress. However, without direct access to the code or the UltraReview system, it's challenging to provide a definitive solution.

Recommendation

Apply workaround: Monitor UltraReview runs and manually refund credits for failed runs, as a permanent fix is not yet available. This approach will help mitigate the issue until a more robust solution is implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Either the run completes and returns findings, or it fails cleanly without consuming credits.

#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] UltraReview timeout/crash consumed ~$37 in credits with no output returned [1 participants]