Quick answer: If the sequence plays in editor but not runtime, the possessable bindings cannot resolve at runtime. Use spawnables for self-contained sequences, or rebind possessables via SetBindingByName before playing. Check “Auto Play” on the Level Sequence Actor is on for sequences that should fire automatically.

Here is how to fix Unreal Sequencer keyframe not evaluating. You author a cinematic in the Level Sequence editor. The camera swoops, the character walks, particles trigger. Press Play in editor — perfect. Launch the game, trigger the cutscene — nothing. Or the camera moves but the character doesn’t animate. Or only half the tracks play. Sequencer’s binding system is powerful but strict about what can be resolved when.

The Symptom

A Level Sequence that plays correctly in editor does not evaluate properly at runtime:

What Causes This

Possessable binding failure. A possessable refers to a specific actor by name. If the referenced actor was destroyed, renamed, or does not exist in the runtime level, binding fails — that track does nothing. Editor preview uses the actor at design time; runtime may not have it.

Spawnable vs possessable confusion. A spawnable is owned by the sequence — spawned on Start, destroyed on End. If you convert a possessable to spawnable, you get a duplicate actor. If you convert spawnable to possessable, the original actor no longer exists.

Auto Play disabled. The Level Sequence Actor has an Auto Play property. If off, the sequence is loaded but not played. You must call Play programmatically.

Playback range wrong. Work Range (editor preview) and Playback Range (runtime limits) are separate. A track outside Playback Range does not play at runtime even though it’s visible in the editor.

Runtime evaluation disabled. Project Settings > Sequencer has options that can disable runtime playback. For shipping builds, make sure sequence evaluation is enabled.

The Fix

Step 1: Convert critical bindings to spawnables. For a cutscene where you do not care about game state — a camera fly-through, a self-contained intro — right-click each binding in the Sequencer outliner and choose “Convert to Spawnable.”

Spawnables are self-contained: the actor data is stored in the sequence, and playing the sequence creates a fresh actor. Runtime binding is automatic.

Step 2: Rebind possessables at runtime. For sequences that target the current player (e.g. “player takes damage and falls down”), keep them as possessables and rebind before playing:

// Rebind possessable to current player
ULevelSequencePlayer* Player = nullptr;
ALevelSequenceActor* SeqActor = nullptr;

UMovieSceneSequencePlayer::CreateLevelSequencePlayer(
    GetWorld(), LevelSequence, FMovieSceneSequencePlaybackSettings(),
    SeqActor);
Player = SeqActor->GetSequencePlayer();

// Get the binding we want to rebind
FMovieSceneObjectBindingID BindingID = GetBindingIDForPlayer();
TArray<UObject*> OverrideArray;
OverrideArray.Add(GetPlayerCharacter());

Player->SetBindingByTag(TEXT("Player"), OverrideArray);
Player->Play();

Use Binding Tags on possessables for this pattern: tag the possessable “Player” in the Sequencer, then rebind by tag at runtime.

Step 3: Verify Auto Play or call Play explicitly. Select the Level Sequence Actor in the level. Auto Play options:

For programmatic triggering, use:

LevelSequenceActor->GetSequencePlayer()->Play();

// Or with options:
FMovieSceneSequencePlaybackSettings Settings;
Settings.LoopCount.Value = 0;
Settings.PlayRate = 1.0f;
SeqActor->GetSequencePlayer()->PlayAt(Settings);

Step 4: Check playback range matches work range. In the Level Sequence editor, the green playback range bar should cover all your keyframes. A playback range that ends before the last keyframe means runtime skips the rest.

Expand the playback range: drag the right green marker, or Sequence Settings > Playback Range > End.

Debugging Binding Resolution

Enable Sequencer verbose logging:

[Core.Log]
LogMovieScene=Verbose
LogLevelSequence=Verbose

Run the game. The log shows binding resolution attempts, successes, failures. “Could not bind” messages tell you exactly which actor could not be found.

Also useful: ke * ListSequences in console shows active sequences and their state in real-time.

Blueprint Play Pattern

In Blueprint, use Create Level Sequence Player node to instantiate, bind parameters, then call Play. Fire on gameplay events (level enter, boss defeated, player death). Attach cleanup logic to OnFinished delegate.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal 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 Unreal. 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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unreal-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 Unreal, 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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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.

“Sequencer is a binding system first and a timeline second. Bindings that cannot resolve are silent failures; learn to check them first.”

Related Issues

For related animation issues, see Skeletal Mesh Merge Not Combining Materials. For actor attachment in cutscenes, AttachActorToComponent Wrong Transform covers related runtime patterns.

Spawnables for self-contained, possessables with tagged rebinds for game-state-aware sequences.