bevyengine/bevy · error · GetProcessorError

The processor '{processor_short_name}' is ambiguous between

Error message

The processor '{processor_short_name}' is ambiguous between several processors: {ambiguous_processor_names:?}

What it means

GetProcessorError::AmbiguousProcessor: the given short name matches more than one registered processor (e.g. the same short name coming from different crates), so the lookup cannot choose which one to use and reports all candidates.

Source

Thrown at crates/bevy_asset/src/processor/mod.rs:1846

    ValidateLogError(#[from] ValidateLogError),
}

/// An error when attempting to set the transaction log factory.
#[derive(Error, Debug)]
pub enum SetTransactionLogFactoryError {
    /// The transaction log is already in use, so setting the factory does nothing.
    #[error("Transaction log is already in use so setting the factory does nothing")]
    AlreadyInUse,
}

/// An error when retrieving an asset processor.
#[derive(Error, Debug, PartialEq, Eq)]
pub enum GetProcessorError {
    /// The processor of that name does not exist.
    #[error("The processor '{0}' does not exist")]
    Missing(String),
    /// The given short name is ambiguous between several processors.
    #[error("The processor '{processor_short_name}' is ambiguous between several processors: {ambiguous_processor_names:?}")]
    Ambiguous {
        /// The given string for the processor name.
        processor_short_name: String,
        /// The list of processors that might match it.
        ambiguous_processor_names: Vec<&'static str>,
    },
}

impl From<GetProcessorError> for ProcessError {
    fn from(err: GetProcessorError) -> Self {
        match err {
            GetProcessorError::Missing(name) => Self::MissingProcessor(name),
            GetProcessorError::Ambiguous {
                processor_short_name,
                ambiguous_processor_names,
            } => Self::AmbiguousProcessor {
                processor_short_name,
                ambiguous_processor_names,

View on GitHub (pinned to 396ca72708)

Solutions

1. Use the fully-qualified processor name to disambiguate
2. Rename one of the conflicting processors at registration

When it happens

Trigger: Thrown at crates/bevy_asset/src/processor/mod.rs:1846 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of bevyengine/bevy@396ca72708 (2026-08-20). Data as JSON: /api/errors/7627524769379ad3. Report an issue: GitHub.