Maximum Execution Time Exceeded in WordPress: What to Check

Short answer: a script exceeded the time PHP allows for a single request (max_execution_time, often 30 seconds) and was terminated. The timeout is a safety mechanism, not the problem. The problem is whatever took that long.

Where it clusters

Timeouts gather around a few operations: plugin and theme updates, imports and exports, backups, bulk edits, image regeneration, and any page that calls a slow external API. If the message appears during ordinary browsing instead, that is a much stronger signal of a performance or database problem worth investigating rather than masking.

Raise it only where it belongs

For a genuine one-off migration you can raise the limit — in wp-config.php with set_time_limit(300); in a maintenance script, or via php.ini/host settings. But raising it on pages real visitors load is a poor permanent answer: it holds server processes open, lowers how many concurrent visitors you can serve, and turns a fast failure into a slow outage.

Find what is slow

1. Identify the exact action that triggers it and whether it is reproducible.
2. Check whether it completes partially — half-finished imports and backups must be cleaned up before retrying, or you get duplicates.
3. Look for slow external calls; a hanging third-party service can stall an otherwise healthy request. Disable that integration temporarily to confirm.
4. Review the slow-query log if your host offers one; an unindexed query on a large table is a common cause.

Move long jobs off the web request

The durable fix for genuinely long-running tasks is to run them via WP-CLI or a scheduled process rather than the browser — a full backup or a large import should never depend on a 30-second web timeout. After changing anything, re-run the operation and confirm it finishes well inside the limit, not just under it.