AI quota exhausted for m30n and blindxfish; quotas not reset, users blocked for days #74

New Issue
Open
opened 2026-07-13 00:37:19 +02:00 by retoor · 8 comments
retoor commented 2026-07-13 00:37:19 +02:00
Owner
Copy Link

Summary

Multiple users have hit their 24-hour AI quota and have not been reset, leaving them unable to use Devii or any AI features. The member cap of $1.00 per 24h is reported as very low.

Steps to Reproduce

  1. As user m30n, attempt an AI request after July 10, 08:15.
  2. Observe the error: "AI request blocked - 24h quota reached".
  3. As user blindxfish, attempt an AI request after July 2, 11:02.
  4. Observe the same error.
  5. As a Guest user, attempt an AI request after July 1, 12:46.
  6. Observe the same error (with a $0.05 limit).

Expected Behaviour

Quotas should reset after 24 hours, or an admin should be able to manually reset or raise caps so affected users can regain access to AI features.

Actual Behaviour

  • m30n has been blocked for 2+ days without quota reset or cap increase.
  • blindxfish has been blocked for 10 days without quota reset or cap increase.
  • Guest user also blocked since July 1.
  • No notification system alerted admins to these blocks.

Environment

Not provided.

Reported by retoor via DevPlace.

## Summary Multiple users have hit their 24-hour AI quota and have not been reset, leaving them unable to use Devii or any AI features. The member cap of $1.00 per 24h is reported as very low. ## Steps to Reproduce 1. As user m30n, attempt an AI request after July 10, 08:15. 2. Observe the error: "AI request blocked - 24h quota reached". 3. As user blindxfish, attempt an AI request after July 2, 11:02. 4. Observe the same error. 5. As a Guest user, attempt an AI request after July 1, 12:46. 6. Observe the same error (with a $0.05 limit). ## Expected Behaviour Quotas should reset after 24 hours, or an admin should be able to manually reset or raise caps so affected users can regain access to AI features. ## Actual Behaviour - m30n has been blocked for 2+ days without quota reset or cap increase. - blindxfish has been blocked for 10 days without quota reset or cap increase. - Guest user also blocked since July 1. - No notification system alerted admins to these blocks. ## Environment Not provided. --- *Reported by **retoor** via DevPlace.*
plan-ticket-74.md
7.4 KiB
typosaurus commented 2026-07-20 00:38:19 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-20 00:38:39 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-20 00:45:46 +02:00
Collaborator
Copy Link

After comparing the ticket against the current source and tests, and reviewing external documentation, the described scenario of quotas never resetting with no manual reset path does not match the codebase. Both automatic 24-hour rolling resets and multiple manual reset tools are already implemented. The core issue appears to be an operational awareness gap and low default caps rather than a code defect. Could you confirm whether this ticket still reflects an accurate requirement, or should it be closed?

After comparing the ticket against the current source and tests, and reviewing external documentation, the described scenario of quotas never resetting with no manual reset path does not match the codebase. Both automatic 24-hour rolling resets and multiple manual reset tools are already implemented. The core issue appears to be an operational awareness gap and low default caps rather than a code defect. Could you confirm whether this ticket still reflects an accurate requirement, or should it be closed?
typosaurus commented 2026-07-23 01:15:45 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-23 01:16:40 +02:00
Collaborator
Copy Link

I need input to continue.

What I tried: Retried this step 3 times.
What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket.

The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.

I need input to continue. What I tried: Retried this step 3 times. What I found: Each attempt failed for internal reasons unrelated to this ticket. The details are in the operator's logs; this is not a judgment about the ticket. The system needs operator attention before I can continue. Reply here once things are healthy and I will resume from where I left off.
typosaurus commented 2026-07-23 02:53:49 +02:00
Collaborator
Copy Link

I am picking this ticket up now.

First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.

I am picking this ticket up now. First I will bring up an isolated workspace with a fresh checkout and investigate whether the ticket matches the current state of the code before planning any change. I will announce every step here before I take it.
typosaurus commented 2026-07-23 02:54:10 +02:00
Collaborator
Copy Link

Starting research round 1 of at most 5.

I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.

Starting research round 1 of at most 5. I am now reading the relevant source, tests, and prior work in the live checkout to verify the ticket and gather the context needed for a concrete plan. This can take a while; I will post periodic progress updates until it completes.
typosaurus commented 2026-07-23 02:57:23 +02:00
Collaborator
Copy Link

The ticket was compared against the current source code, tests, and external documentation. The investigation confirms that the rolling 24-hour quota window, manual reset endpoints, and admin notifications all exist and function as designed. The reported behavior— quotas failing to reset automatically and administrators being unable to unblock users—does not correspond to any code defect.

This discrepancy suggests the issue is operational or configurational rather than a software problem. Could you confirm whether this description is still accurate, or should the ticket be closed?

The ticket was compared against the current source code, tests, and external documentation. The investigation confirms that the rolling 24-hour quota window, manual reset endpoints, and admin notifications all exist and function as designed. The reported behavior— quotas failing to reset automatically and administrators being unable to unblock users—does not correspond to any code defect. This discrepancy suggests the issue is operational or configurational rather than a software problem. Could you confirm whether this description is still accurate, or should the ticket be closed?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#74
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?