prestodb/presto · error · PrestoException

PROCEDURE_NOT_FOUND

PROCEDURE_NOT_FOUND

Error message

Procedure not registered: 

What it means

PrestoException (PROCEDURE_NOT_FOUND) from BuiltInProcedureRegistry.resolve: no procedure is registered for the requested connector and schema-qualified procedure name, meaning either the name is wrong or the connector exposes no such procedure.

Source

Thrown at presto-main-base/src/main/java/com/facebook/presto/metadata/BuiltInProcedureRegistry.java:97

    }

    @Override
    public void removeProcedures(ConnectorId connectorId)
    {
        connectorProcedures.remove(connectorId);
    }

    @Override
    public BaseProcedure<?> resolve(ConnectorId connectorId, SchemaTableName name)
    {
        Map<SchemaTableName, BaseProcedure<?>> procedures = connectorProcedures.get(connectorId);
        if (procedures != null) {
            BaseProcedure<?> procedure = procedures.get(name);
            if (procedure != null) {
                return procedure;
            }
        }
        throw new PrestoException(PROCEDURE_NOT_FOUND, "Procedure not registered: " + name);
    }

    @Override
    public DistributedProcedure resolveDistributed(ConnectorId connectorId, SchemaTableName name)
    {
        Map<SchemaTableName, BaseProcedure<?>> procedures = connectorProcedures.get(connectorId);
        if (procedures != null) {
            BaseProcedure<?> procedure = procedures.get(name);
            if (procedure instanceof DistributedProcedure) {
                return (DistributedProcedure) procedure;
            }
        }
        throw new PrestoException(PROCEDURE_NOT_FOUND, "Distributed procedure not registered: " + name);
    }

    @Override
    public boolean isDistributedProcedure(ConnectorId connectorId, SchemaTableName name)
    {

View on GitHub (pinned to 55bb57d202)

Solutions

1. Verify the procedure name, schema, and catalog (e.g. system.sync or a connector schema)
2. Confirm the connector actually registers the procedure in its ConnectorMetadata
3. Check for typos in the CALL statement's qualified name

When it happens

Trigger: Thrown at presto-main-base/src/main/java/com/facebook/presto/metadata/BuiltInProcedureRegistry.java:97 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of prestodb/presto@55bb57d202 (2026-09-04). Data as JSON: /api/errors/1e7a266001fe1d12. Report an issue: GitHub.