bevyengine/bevy · error · InitializeError

Failed to validate asset log: {0}

Error message

Failed to validate asset log: {0}

What it means

InitializeError::ValidateLogError: wrapping a ValidateLogError produced while the asset processor read and validated its transaction log during initialization. It fires when log entries are duplicated, mismatched, or unreadable, meaning prior processing state cannot be trusted.

Source

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

pub enum ProcessorState {
    /// The processor is still initializing, which involves scanning the current asset folders,
    /// constructing an in-memory view of the asset space, recovering from previous errors / crashes,
    /// and cleaning up old / unused assets.
    Initializing,
    /// The processor is currently processing assets.
    Processing,
    /// The processor has finished processing all valid assets and reporting invalid assets.
    Finished,
}

/// An error that occurs when initializing the [`AssetProcessor`].
#[derive(Error, Debug)]
pub enum InitializeError {
    #[error(transparent)]
    FailedToReadSourcePaths(AssetReaderError),
    #[error(transparent)]
    FailedToReadDestinationPaths(AssetReaderError),
    #[error("Failed to validate asset log: {0}")]
    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.

View on GitHub (pinned to 396ca72708)

Solutions

1. Follow the inner ValidateLogError variant for the specific cause
2. Delete the processed asset folder to force full reprocessing
3. Avoid running multiple processor instances against the same imported directory

When it happens

Trigger: Thrown at crates/bevy_asset/src/processor/mod.rs:1827 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/fe8f966abf0e546c. Report an issue: GitHub.