hasura/graphql-engine · error · Error

Internal error from plugin {plugin_name}

Error message

Internal error from plugin {plugin_name}

What it means

The pre-NDC-response plugin reported an internal error in its structured payload. The engine passes through the plugin name and the raw JSON error detail. This is a failure inside the plugin itself (bug, dependency failure, panic), not an invalid engine request or an unreachable endpoint.

Source

Thrown at v3/crates/plugins/pre-ndc-response-plugin/src/execute.rs:26

    header::{InvalidHeaderName, InvalidHeaderValue},
};
use serde::{Deserialize, Serialize};
use std::{collections::BTreeMap, str::FromStr, sync::Arc};
use tracing_util::{ErrorVisibility, SpanVisibility, TraceableError, set_attribute_on_active_span};

#[derive(Debug, thiserror::Error)]
pub enum Error {
    #[error("Error while making the HTTP request to the pre-response plugin {0} - {1}")]
    ErrorWhileMakingHTTPRequestToTheHook(String, reqwest::Error),
    #[error("Error while building the request for the pre-response plugin {0} - {1}")]
    BuildRequestError(String, #[source] BuildRequestError),
    #[error("Reqwest error: {0}")]
    ReqwestError(reqwest::Error),
    #[error("Unexpected status code: {0}")]
    UnexpectedStatusCode(u16),
    #[error("Error parsing the request: {0}")]
    PluginRequestParseError(serde_json::error::Error),
    #[error("Internal error from plugin {plugin_name}")]
    PluginInternalError {
        plugin_name: String,
        error: serde_json::Value,
    },
    #[error("User error from plugin {plugin_name}")]
    PluginUserError {
        plugin_name: String,
        error: serde_json::Value,
    },
}

#[derive(Debug, thiserror::Error)]
pub enum BuildRequestError {
    #[error("Invalid header name {header_name}: {error}")]
    InvalidHeaderName {
        header_name: String,
        #[source]
        error: InvalidHeaderName,

View on GitHub (pinned to 724551b9ae)

Solutions

1. Read the passthrough error JSON — it carries the plugin's own message/details
2. Inspect the plugin process logs at the timestamp of the failure
3. Reproduce with the same response payload to find the crashing code path
4. Pin a known-good plugin version if a recent update introduced the failure

if let Err(Error::PluginInternalError { plugin_name, error }) = res {
    // alert plugin owner with passthrough detail; do not retry
}

When it happens

Trigger: The hook responds with its internal-error body/status and the engine maps it to PluginInternalError { plugin_name, error }.

Common situations: Post-processing plugin crashing on an edge-case response shape; plugin losing connection to its own backing service; out-of-memory or timeout inside the plugin runtime.

Related errors

• Internal error from plugin {plugin_name}
• Error parsing the request: {0}
• User error from plugin {plugin_name}
• Error parsing the request: {0}
• {0}

AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28). Data as JSON: /api/errors/a509d1778dc013d0. Report an issue: GitHub.