bevyengine/bevy · error · LogEntryError

An asset started processing but never finished: {0}

Error message

An asset started processing but never finished: {0}

What it means

LogEntryError variant reporting an unfinished transaction: the log shows an asset began processing but the matching completion entry is missing, usually because the processor crashed or was interrupted mid-processing. Validation fails and all assets are reprocessed.

Source

Thrown at crates/bevy_asset/src/processor/log.rs:282

    /// A [`ReadLogError`].
    #[error("Failed to read log entries: {0}")]
    ReadLogError(BevyError),
    /// Duplicated process asset transactions occurred.
    #[error("Encountered a duplicate process asset transaction: {0:?}")]
    EntryErrors(Vec<LogEntryError>),
}

/// An error that occurs when validating individual [`ProcessorTransactionLog`] entries.
#[derive(Error, Debug)]
pub enum LogEntryError {
    /// A duplicate process asset transaction occurred for the given asset path.
    #[error("Encountered a duplicate process asset transaction: {0}")]
    DuplicateTransaction(AssetPath<'static>),
    /// A transaction was ended that never started for the given asset path.
    #[error("A transaction was ended that never started {0}")]
    EndedMissingTransaction(AssetPath<'static>),
    /// An asset started processing but never finished at the given asset path.
    #[error("An asset started processing but never finished: {0}")]
    UnfinishedTransaction(AssetPath<'static>),
}

View on GitHub (pinned to 396ca72708)

Solutions

1. Delete the imported/processed asset folder to reset state
2. Restart the processor so interrupted assets are reprocessed

When it happens

Trigger: Thrown at crates/bevy_asset/src/processor/log.rs:282 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/fb3c7c72e1a3686f. Report an issue: GitHub.