How do Blueprint Async Actions work?

They’re proxy objects (UBlueprintAsyncActionBase subclasses) created when you call the async node. The proxy listens for completion (load done, timer expired, etc.) and broadcasts the corresponding exec output pin via a multicast delegate. If the proxy is garbage collected before completion, no event fires.

Why do my async load events never fire?

The proxy went out of scope. Hold a reference: in the Blueprint, drag from the proxy output and promote to a variable (or simply have any exec pin downstream of it). In C++, the static factory must return a strong reference, not a weak.

What's the activation pin?

Most async actions have an exec input that triggers activation. If you don’t wire this from the begin pin to the action, the action stays inert. Look at the auto-generated node — the input pin must be connected for the action to start.

Fix: Unreal Blueprint Async Action Not Completing

Quick answer: Hold a hard reference to the async proxy. Wire the activation exec pin. Pass a valid WorldContextObject if the node requires one.

A login flow uses an async “HTTP Get JSON” Blueprint node. The OnSuccess and OnFailure pins both stay silent. The HTTP request fires (you can see it in logs) but the corresponding delegate never broadcasts. The async proxy was garbage collected mid-flight.

Async Action Object Lifetimes

Blueprint async actions are UObject proxies. When the node runs, it constructs a proxy, registers it with the world, and waits for an event. The proxy holds the multicast delegate that fires completion exec pins.

If nothing keeps the proxy alive (no exec pin downstream wired, no variable storing it), the GC may collect it before the completion event fires. The async source completes, tries to broadcast, finds the proxy gone, nothing happens.

Fix 1: Wire Downstream Pins

Drag from each completion pin (OnSuccess, OnFailure) to a subsequent node, even a Print String. Wiring counts as a reference; the proxy stays alive.

If you want async behavior “fire and forget” with no downstream — still wire at least one downstream node (a no-op like Print) per output pin. Or store the proxy in a variable.

Fix 2: Promote to Variable

Drag from the proxy output of the node (often labeled the action’s name) and right-click → Promote to Variable. The variable holds a hard reference, keeping the proxy alive until the variable goes out of scope.

Fix 3: Verify WorldContextObject

Many async nodes have a hidden WorldContextObject parameter. If the calling Blueprint isn’t in a world (e.g., editor utility), the world context is null and the action may fail silently. Call from a Blueprint that lives in a world, or pass Self explicitly for nodes that expose the parameter.

Fix 4: Check Async Action’s Activation

// Custom async action in C++
UCLASS()
class UMyAsyncAction : public UBlueprintAsyncActionBase
{
    GENERATED_BODY()
public:
    UPROPERTY(BlueprintAssignable) FMySimpleDelegate OnComplete;

    UFUNCTION(BlueprintCallable, meta = (BlueprintInternalUseOnly = "true", WorldContext = "WorldContextObject"))
    static UMyAsyncAction* DoAsync(UObject* WorldContextObject);

    virtual void Activate() override;
};

The static factory returns a UMyAsyncAction* — Blueprint captures the returned proxy. Activate is called by Blueprint after the factory; this is where you kick off the underlying async work. Forgetting to override Activate = nothing happens.

Diagnosing

Set a breakpoint on the proxy’s completion delegate broadcast. If it’s reached but no listeners run, the proxy is alive but Blueprint listeners died (Blueprint object destroyed). If never reached, the underlying work didn’t complete or you didn’t wire activation.

Verifying

Trigger the async node. OnSuccess or OnFailure should fire within the expected time. If neither fires, recheck the four-step list. Use obj list in console to see if your proxy class is alive in memory.

“Async proxies need someone to hold them alive. Wire pins, promote to variable, or write your factory to return a hard reference.”

When auditing async-action bugs, always check if downstream pins are wired — the most common silent-failure cause.