Significant-Gravitas/AutoGPT · warning · HTTPException

Your weekly limit is also reached. Resetting the daily limit

Error message

Your weekly limit is also reached. Resetting the daily limit won't help.

What it means

HTTP 400 from POST /usage/reset (routes.py:1092). Even when the daily limit is exhausted, the endpoint checks the weekly limit too: if weekly usage >= weekly_limit, clearing the daily counter changes nothing because the weekly cap still blocks the user. The comment in source says 'Resetting the daily limit won't help.' The request is rejected before any credits are charged.

Source

Thrown at autogpt_platform/backend/backend/api/features/chat/routes.py:1092

        # Verify the user is actually at or over their daily limit.
        # (rate_limit_reset_cost intentionally omitted — this object is only
        # used for limit checks, not returned to the client.)
        usage_status = await get_usage_status(
            user_id=user_id,
            daily_cost_limit=daily_limit,
            weekly_cost_limit=weekly_limit,
            tier=tier,
        )
        if daily_limit > 0 and usage_status.daily.used < daily_limit:
            raise HTTPException(
                status_code=400,
                detail="You have not reached your daily limit yet.",
            )

        # If the weekly limit is also exhausted, resetting the daily counter
        # won't help — the user would still be blocked by the weekly limit.
        if weekly_limit > 0 and usage_status.weekly.used >= weekly_limit:
            raise HTTPException(
                status_code=400,
                detail="Your weekly limit is also reached. Resetting the daily limit won't help.",
            )

        # Charge credits.
        credit_model = await get_user_credit_model(user_id)
        try:
            remaining = await credit_model.spend_credits(
                user_id=user_id,
                cost=cost,
                metadata=UsageTransactionMetadata(
                    reason="CoPilot daily rate limit reset",
                ),
            )
        except InsufficientBalanceError as e:
            raise HTTPException(
                status_code=402,
                detail="Insufficient credits to reset your rate limit.",

View on GitHub (pinned to 9c8bb5550f)

Solutions

Wait for the weekly window to reset (Monday 00:00 UTC) — no paid reset can bypass it.
If the product allows, raise weekly_cost_limit_microdollars for the user's tier.
Client-side: when the usage status shows weekly exhaustion, show a weekly-reset countdown instead of the daily reset button to avoid the 400.

Example fix

// before
// only daily state checked in UI -> users at weekly cap still click reset

// after — check both windows
const blocked = usage.daily.used >= usage.daily.limit
  || usage.weekly.used >= usage.weekly.limit;
{blocked && usage.weekly.used < usage.weekly.limit && <ResetButton />}

Defensive patterns

Strategy: validation

Validate before calling

// check both windows before offering the paid daily reset
const u = await getUsageStatus();
const dailyExhausted = u.daily.used >= u.daily.limit;
const weeklyExhausted = u.weekly.used >= u.weekly.limit;
if (dailyExhausted && !weeklyExhausted) await post('/chat/usage/reset');
else if (weeklyExhausted) showWeeklyResetCountdown();

Try / catch

try { await post('/chat/usage/reset'); } catch (e) { if (e.status === 400 && /weekly limit/.test(e.detail)) { showWeeklyResetCountdown(); return; } throw e; }

Prevention

Always render the weekly cap alongside the daily one in limit UIs
Never offer a paid reset when the weekly cap is exhausted — it cannot help
Weekly window resets Monday 00:00 UTC; show that countdown

When it happens

Trigger: User is at/over both daily and weekly cost limits (weekly_cost_limit_microdollars, default 5,000,000 = $5/week, resets Monday 00:00 UTC) and calls /usage/reset.

Common situations: End of a heavy week: user hit the weekly cap and keeps seeing the daily-limit error; UI only surfaces the daily message so users buy-reset in confusion; support loads on weekends before the Monday UTC reset.

Related errors

AI-assisted analysis of Significant-Gravitas/AutoGPT@9c8bb5550f (2026-08-14). Data as JSON: /api/errors/67570ffd631c56ae. Report an issue: GitHub.