phalcon/cphalcon · error · NoListenersForEvent

No listeners attached for event {}

Error message

No listeners attached for event {}

What it means

Error "No listeners attached for event {}" thrown in phalcon/cphalcon.

Source

Thrown at phalcon/Events/Manager.zep:436

        bool collect, hasFullQueue, hasTypeQueue;

        // Manager-level kill switch - halt() trips this and every fire
        // returns null without dispatching until resume() clears it.
        if this->halted {
            return null;
        }

        if this->beforeFire(eventType, source, data, cancelable) === false {
            return null;
        }

        // Fast exit on a manager with no listeners attached at all.
        // Done BEFORE parsing the eventType so a misformed name (no
        // colon) doesn't raise "Invalid event type" on a manager that
        // would have had nothing to dispatch to anyway.
        if empty this->events {
            if unlikely this->strict {
                throw new NoListenersForEvent(eventType);
            }

            return null;
        }

        // Cache hit: the eventType parse is deterministic, and the same
        // names fire over and over (db:beforeQuery × N per request etc.).
        // After warm-up this collapses to a single hash lookup.
        if fetch cached, this->eventNameCache[eventType] {
            let type      = cached[0];
            let eventName = cached[1];
        } else {
            let colonPos = strpos(eventType, ":");

            if unlikely colonPos === false {
                throw new InvalidEventType(eventType);
            }

View on GitHub (pinned to b7419de9cd)

When it happens

Trigger: Thrown at phalcon/Events/Manager.zep:436 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of phalcon/cphalcon@b7419de9cd (2026-08-21). Data as JSON: /api/errors/85533b4ffeee7475. Report an issue: GitHub.