Timeout

ESX.SetTimeout runs a function once after a delay, like FiveM's SetTimeout, but returns an id so you can cancel it with ESX.ClearTimeout. Both work on client and server.

OverviewCopy Anchor Link

FunctionsCopy Anchor Link

ESX.SetTimeoutCopy Anchor Link

ESX.SetTimeout(msec, cb)

Returns: number, the timeout id.

local handcuffTimers = {}

RegisterNetEvent('police:cuffed', function(target)
    local xPlayer = ESX.GetPlayerFromId(source)
    if not xPlayer or xPlayer.job.name ~= 'police' then return end

    handcuffTimers[target] = ESX.SetTimeout(10 * 60 * 1000, function()
        handcuffTimers[target] = nil
        TriggerClientEvent('police:forceUncuff', target)
    end)
end)

ESX.ClearTimeoutCopy Anchor Link

ESX.ClearTimeout(id)

Returns: nothing

RegisterNetEvent('police:uncuffed', function(target)
    if handcuffTimers[target] then
        ESX.ClearTimeout(handcuffTimers[target])
        handcuffTimers[target] = nil
    end
end)

Common issuesCopy Anchor Link

• Timers live in es_extended. ESX.SetTimeout runs inside es_extended, so restarting es_extended drops all pending timeouts. If your own resource restarts first, its callbacks can no longer run.
• Clearing twice is harmless, but clearing an id that already ran leaves a small entry behind. Set your stored id to nil after the callback runs, as in the example.

RelatedCopy Anchor Link

• Shared functions (ESX.Await)
• Table functions
• Performance guide

Frequently asked questions