Fix: Unity Visual Scripting Graph Not Running On Awake

Here is how to fix Unity Visual Scripting graphs whose On Awake node never executes. Your scene plays fine, no errors are logged, but the entry node sits unhighlighted while the rest of the graph waits for input that never comes. Visual Scripting’s lifecycle nodes have specific timing requirements, and in builds the situation is complicated by an AOT pre-build step that is easy to forget.

The Symptom

You build a Script Machine graph that begins with On Awake, wired to setup logic. In Play mode, the setup never runs. The graph editor shows no orange highlight on the Awake node when entering Play mode. Other event nodes (like On Update) work fine.

In a build, an even broader symptom: the entire graph does nothing on iOS or Switch, but works in editor.

What Causes This

Script Machine added at runtime. If your code adds ScriptMachine via AddComponent, Awake has already fired on the GameObject. The new component initializes too late to receive the event.

Graph asset assigned after activation. The Script Machine has Source set to Graph and a public field for the asset. If your asset is loaded asynchronously and assigned after Awake, the graph misses its own Awake.

OnEnable vs Awake confusion. Pooled objects are typically deactivated and reactivated, but Awake only fires the first time. Pulling an object from a pool will not re-fire Awake.

AOT pre-build missing for IL2CPP. Visual Scripting uses runtime reflection for user types. IL2CPP strips reflection metadata. The fix is the AOT pre-build step that generates link.xml entries and stub assemblies.

The Fix

Step 1: Use OnEnable for setup that must always run.

In your graph, replace On Awake with On Enable. OnEnable fires when the GameObject activates and again on every reactivation. For pooled objects this is the right hook.

Step 2: Confirm the graph asset is assigned in the inspector at edit time. Avoid loading graphs at runtime if you need Awake to fire reliably. If you must load dynamically, use OnEnable inside the graph and toggle the GameObject inactive/active after assignment:

using UnityEngine;
using Unity.VisualScripting;

public class RuntimeGraphLoader : MonoBehaviour
{
    [SerializeField] private ScriptGraphAsset graph;

    void Start()
    {
        gameObject.SetActive(false);
        var sm = gameObject.AddComponent<ScriptMachine>();
        sm.nest.source = GraphSource.Macro;
        sm.nest.macro = graph;
        gameObject.SetActive(true);  // Now OnEnable fires on the graph
    }
}

Step 3: Run AOT pre-build before building for IL2CPP. Open Edit → Project Settings → Visual Scripting, scroll to the AOT Pre-build section, and click Build Pre-built Assemblies. Re-run this any time you add new node types or third-party Visual Scripting integrations.

Step 4: Add types to the type options. If your graph references custom MonoBehaviour types, those must be in Project Settings → Visual Scripting → Type Options. After adding, click Regenerate Units.

Step 5: Verify execution with a debug log. Drop a Log node directly off the entry event. If the log appears, the entry fired. If not, the entry node is the problem.

State Machine vs Script Machine

State Machines have their own lifecycle: On Enter State fires when a state becomes active. If you put logic in a State graph and expect Awake-style behavior, use On Enter State on the initial state instead. Awake nodes inside a State graph only fire if that state is active when the State Machine itself awakes.

Pooling Pitfall

Object pooling is the most common reason Awake nodes seem unreliable. The first activation fires Awake correctly. Every subsequent reuse from the pool does not. Always use OnEnable for per-spawn initialization.

Understanding the issue

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. 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

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

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 Unity-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 Unity, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Awake fires once. OnEnable fires forever. For setup that must repeat, OnEnable is the right hook.”

Related Issues

For runtime IL2CPP failures, see IL2CPP Managed Stripping. For pooling state issues, see Object Pooling Returning Wrong State.

OnEnable for repeating setup. AOT pre-build before every IL2CPP build. The graph runs.