Fix MySQL max_questions Resource Limit Errors

Fix MySQL “max_questions resource” errors

The database account has reached its configured hourly query limit. MySQL rejects more queries for that account until the counter resets or an administrator changes the account limit.

Applies to

MySQL accounts with per-hour resource limits

Reviewed

August 3, 2026

First published

2010-06-25

What the message means

MySQL counts queries per account, not per browser or application session. Multiple WordPress workers using the same database account contribute to the same hourly total.

The database may recover when the provider’s hourly counter resets, but a recurring error needs a capacity or query-volume fix.

Resolve the immediate failure

Capture the complete error and time, then confirm which database account and site are affected.
Contact the hosting provider or database administrator to confirm the configured MAX_QUERIES_PER_HOUR value and reset policy.
Ask whether the plan can raise or remove the limit. MySQL uses zero to represent no per-hour account limit.
If traffic does not explain the usage, review slow-query logs, repeated background jobs, failing retries, and plugins or custom code that issue excessive queries.

Avoid misleading fixes

Opening more application connections does not bypass an account-level query limit; their queries are counted together.
Restarting WordPress does not change a limit stored on the MySQL account.
Do not publish database credentials or full connection strings when requesting support.