Skip to content

fix(api): pause keyed Hypixel requests until a 429's reset - #1044

Open
ugcodrr wants to merge 5 commits into
fix/hypixel-rate-limit-fallbackfrom
fix/hypixel-429-pause
Open

ugcodrr wants to merge 5 commits into
fix/hypixel-rate-limit-fallbackfrom
fix/hypixel-429-pause

Conversation

@ugcodrr

@ugcodrr ugcodrr commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Description: While Hypixel rate limits Statsify, every lookup still calls Hypixel and gets another 429, and the bot can't say when to try again.

  1. A response saying no requests are left starts the pause too, before the 429.
  2. With nothing cached, the bot says how long until the limit resets instead of "Hypixel API Unavailable".

Testing: After Hypixel answers a 429, /bedwars for a player that was never looked up says "Statsify has reached its Hypixel API limit. Please try again in about 1 minute!" until the reset.

Conflicts with #997 in packages/discord/src/services/api.service.ts.

Depends on #985

@vercel

vercel Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
statsify Ignored Ignored Nov 5, 2026 8:19am UTC

@vercel

vercel Bot commented Nov 2, 2026

Copy link
Copy Markdown

Deployment failed for project statsify with the following error:

Resource is limited - try again in 1 day (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/statsify-net?upgradeToPro=build-rate-limit

@vercel

vercel Bot commented Nov 3, 2026

Copy link
Copy Markdown

Deployment failed for project statsify with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/statsify-net?upgradeToPro=build-rate-limit

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant