Quick answer: Check that timeout is connected to a handler, process_mode is not Disabled, and the Timer’s parent tree is not paused. Timers fire independently of your script — the problem is almost always signal wiring or a paused tree.

Here is how to fix Godot Timer autostart not firing. You add a Timer node, set wait_time to 2.0, check Autostart. You connect timeout to a method. You run the scene. Nothing happens. Two seconds pass, four, ten — the timeout handler never fires. Timer is one of Godot’s simpler nodes but has a few gotchas that produce silent silence.

The Symptom

A Timer with Autostart and a connected timeout signal does not produce any timeout events. The handler function never runs. No error. timer.is_stopped() may return true (it never started) or false (it is running but signal is not connected).

What Causes This

timeout signal not connected. Autostart starts the timer counting down. But without a connection to the timeout signal, nothing happens when it reaches zero except the signal fires into the void. In the editor, check the Node panel’s Signals tab — timeout should have a green dot indicating connection.

Handler method renamed or missing. If you had a connection to _on_timer_timeout and renamed the method to _on_my_timer_timeout, the signal connection still points to the old name. Godot silently leaves the connection broken.

Process mode disabled or wrong. A Timer with process_mode = PROCESS_MODE_DISABLED does not tick. A Timer in a paused tree also does not tick unless its process_mode is ALWAYS.

Autostart set in code after scene load. Setting autostart = true in _ready() is too late — autostart is a property read during node initialization, not when _ready fires. Set via editor or call start() explicitly in _ready.

one_shot with expectations of repeat. With one_shot = true, the timer fires once and stops. If you wanted recurring fires, the second timeout never comes.

The Fix

Step 1: Verify signal connection in editor. Select the Timer node. In the Node dock (right side), switch to the Signals tab. Find timeout(). Click to connect. Pick the script and method. The method appears in the script with a pre-filled body.

extends Node

@onready var timer: Timer = $Timer

func _ready():
    # Code-side connection as alternative
    timer.timeout.connect(_on_timer_timeout)

func _on_timer_timeout():
    print("Timer fired!")

Use either editor connection OR code connection — not both, or you get duplicate firings. If unsure, prefer code connections; they survive renames when you use the method reference.

Step 2: Configure Timer properties. In the Inspector:

Step 3: Trigger explicitly if autostart misbehaves. If Autostart is unreliable due to scene loading order, call start() in _ready:

func _ready():
    $Timer.start() # force-start regardless of autostart value

Step 4: Handle paused trees. For a Timer on a node tree that can be paused (game pause), set process_mode = PROCESS_MODE_ALWAYS so the timer keeps running:

func _ready():
    $PauseMenuTimer.process_mode = Node.PROCESS_MODE_ALWAYS

Without this, pause stops the timer along with gameplay, which may or may not be what you want.

Awaiting Timeout

An alternative to signals: await the timeout directly:

func do_delayed_action():
    var t = get_tree().create_timer(2.0)
    await t.timeout
    print("Two seconds later")

This uses SceneTree’s create_timer instead of a Timer node. Simpler for one-shot delays in coroutine-style code. No signal connection needed.

Debugging Checklist

If Timer still does not fire:

  1. Print state: print(timer.is_stopped(), timer.time_left) in _process — you see whether it is running
  2. Add a debug timeout.connect(func(): print("fired")) to verify at least one handler exists
  3. Check that the Timer is actually added to the tree — an orphaned Timer does not tick
  4. Confirm the scene is playing (F6 single scene or F5 project)

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Timers are simple. When one does not fire, the answer is almost always signal connection or process mode.”

Related Issues

For AnimationPlayer issues, see AnimationPlayer Not Playing on Ready. For await-based patterns, Await Signal Never Completing covers related async issues.

Signal connected, process_mode not disabled, scene not paused. Three checks, Timer fires.