claude-code - 💡(How to fix) Fix ultrareview: free run consumed when server-side rate-limited (run crashed before producing findings) [1 comments, 1 participants]

Ran /ultrareview on a PR. The run crashed and returned {"error":"Review crashed before producing findings. See session logs for details."}. Subsequent message in the terminal: API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited. 2. Consider treating `error.code == rate_limited` server-side as non-billing for ultrareview (no findings = no charge).

TL;DR

The issue can be mitigated by requesting a refund for the consumed free run and potentially treating server-side rate limiting errors as non-billing events for ultrareview.

Guidance

• Verify the session logs for the crashed run (session_01QUQLCvLb5eN2ACQEJc3bk7) to confirm the cause of the crash and ensure it was indeed due to server-side rate limiting.
• Reach out to support to request a refund for the consumed free run, as the user did not receive the deliverable.
• Consider providing feedback to the development team to treat error.code == rate_limited server-side errors as non-billing events for ultrareview, to prevent similar issues in the future.
• Review the usage limits and plan details to understand how the free executions are being tracked and consumed.

Notes

The issue seems to be related to the server-side rate limiting and the billing mechanism for ultrareview executions. The user has already consumed one of their free executions, and it's unclear if this will be automatically refunded or if manual intervention is required.

Recommendation

Apply workaround: Request a refund for the consumed free run and provide feedback to the development team to consider treating server-side rate limiting errors as non-billing events. This approach allows the user to recover the lost execution and potentially prevents similar issues in the future.