Performancewarning
[resourceName] script timeout / hitch warning
Also seen as: script timeout FiveM hitch warning server thread hitch resource took too long
What causes it
A resource held the single main server thread too long to finish a tick on time. The number is the delay in milliseconds. Almost always a Lua loop missing a Wait(), or a synchronous/blocking database call.
How to fix it
Find the resource named in the warning and fix the blocking code — usually a missing Wait() in a loop.
- Note which resource name appears next to the hitch/timeout warning.
- Look for a
while true doloop with noWait()— add an appropriateWait(). - Look for synchronous database calls that block; make them async.
- One hitch during a restart is normal; repeated or multi-second hitches mean real blocking work.
- Use the profiler and resmon to confirm the offending resource.
Related errors
Related guides
Still stuck? We can help.
Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.