Error prevents completion of request. #7626
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
This happened at the end of the last month (billing cycle) too. It resolved after a day but it would be nice if it didn't occur at all.
Debugging ID {"conversation_id":"a9495a8e-7b6c-42f6-8a59-70034ac7421d"}
I'm sorry, I couldn't complete that request.
Request failed with error: ErrorStatus(500, "{"error":"Internal server error: Unable to find next billing cycle for stripe overages"}")
This message makes very little sense to me because I am pretty sure that I haven't actually used up my allocation of 2500 requests.
If I may be allowed to speculate: It could be due to a timezone problem
- here in New Zealand it is 14:41 NZDT on 1/10/2025
- in CA, USA it is 18:41 PDT on 30/09/2025
To reproduce
I restart, select the conversation from the previous session and give it the same instruction/request as last time.
Expected behavior
I expect that I can keep using Warp during this NZDT, PDT change over period at the end of the month.
Screenshots, videos, and logs
Operating system (OS)
Windows
Operating system and version
Windows 11
Shell Version
zsh 5.9 (x86_64-ubuntu-linux-gnu) (running on WSL2
Current Warp version
v0.2025.09.24.08.11.stable_03
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
1/10/2025
Additional context
I worked an hour ago and then I clicked on Open admin panel in the Billing and usage tab of Settings. I was unable to login - actually I am surprised that I needed to login as I think this has just automatically logged me in.
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None