Why does my Godot Tween finished signal not emit?

create_tween() returns a Tween bound to the calling node's tree. If the node is freed before the tween completes, the tween is killed and finished never fires. Also, tweens with set_loops() configured to infinite never reach the finished state by definition.

How do I tell when a Godot tween step completes?

Tween emits step_finished(int idx) for each call in the chain plus loop_finished(int loop_count) at the end of each loop iteration. Use these for fine-grained control. The finished signal only fires when the entire tween completes (all loops, all steps).

Why does my parallel tween chain only fire finished once?

finished fires when the whole tween completes regardless of how many parallel branches exist. Each parallel call inside a tween is part of the same tween. To detect when an individual parallel branch completes, use a callback inserted via tween_callback at the desired moment.

Fix: Godot Tween Finished Signal Not Firing

Quick answer: Tween created via create_tween() is owned by the scene tree of the calling node. If the node is freed mid-tween, the tween is killed and finished never emits. Infinite loops also never finish by design. For step-by-step callbacks use step_finished or insert tween_callback.

Here is how to fix Godot 4 Tween finished signals that never emit. Your tween animates correctly, the value reaches its target, but the connected finished handler never runs. Either the tween is being killed prematurely, or you have it configured for infinite loops, or you mistook step_finished for the right signal.

The Symptom

You call create_tween(), chain a few tween_property calls, connect tween.finished to a handler. The animation plays correctly. The handler never runs. Or it runs only sometimes, when the calling node happens to survive long enough.

What Causes This

Owner node freed. create_tween() returns a tween whose lifetime is tied to the calling node. When the owner is freed (scene change, queue_free), the tween is also freed and never emits finished.

Infinite loops. tween.set_loops(0) means infinite. The tween never finishes, so finished never fires.

Tween killed. If you call tween.kill() for any reason — or if pause_mode interactions kill it — finished is skipped.

Wrong signal name. step_finished fires per step in the chain. loop_finished fires per loop iteration. Only finished fires when the whole tween completes.

The Fix

Step 1: Connect to the right signal.

extends Node2D

func _ready():
    var tween = create_tween()
    tween.tween_property(self, "position", Vector2(200, 0), 1.0)
    tween.tween_property(self, "modulate:a", 0.0, 0.5)
    tween.finished.connect(_on_tween_done)

func _on_tween_done():
    print("Tween complete")
    queue_free()

Step 2: Use callbacks for mid-chain hooks.

func _ready():
    var tween = create_tween()
    tween.tween_property(self, "position:x", 200, 1.0)
    tween.tween_callback(_after_first)
    tween.tween_property(self, "position:y", 100, 1.0)

func _after_first():
    print("First leg done")

Step 3: Detect step completion.

var tween = create_tween()
tween.tween_property(self, "position", Vector2(100, 0), 1.0)
tween.tween_property(self, "position", Vector2(100, 100), 1.0)
tween.step_finished.connect(func(idx): print("Step ", idx, " done"))

Step 4: Survive scene transitions with explicit ownership. If the tween must outlive its node, create it on a long-lived node (autoload or HUD root):

# Autoload script TweenHost.gd
extends Node

func tween_for(target: Node) -> Tween:
    return create_tween()

# Calling code
var tween = TweenHost.tween_for(self)
tween.tween_property(self, "modulate:a", 0.0, 0.5)
tween.finished.connect(_on_done)

Step 5: Avoid infinite loops if you need finished. Use set_loops(N) with a finite N. Each iteration emits loop_finished(idx); after the Nth, finished fires.

Common Pitfalls

Connecting finished in _ready on a tween created in _ready works only if the node lives long enough for the tween to complete. For instances spawned and freed quickly (projectiles, hit effects), prefer await:

func shake_then_die():
    var tween = create_tween()
    tween.tween_property(self, "position:x", position.x + 10, 0.05)
    tween.tween_property(self, "position:x", position.x, 0.05)
    await tween.finished
    queue_free()

The await guarantees the next line runs after the tween completes. If the node is freed first, await never resumes, but you also do not need it to.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“Tween lifetime equals owner lifetime. Outlive the node and you outlive the tween. Use awaits or autoload hosts.”

Related Issues

For animation tree state issues, see AnimationTree State Machine. For signal disconnect issues, see Signal Lost After Scene Reload.

Connect finished. Use callbacks for steps. Await for short-lived nodes. The signal fires when it should.