bevyengine/bevy · error · LogEntryError

A transaction was ended that never started {0}

Error message

A transaction was ended that never started {0}

What it means

LogEntryError variant signalling that the transaction log contains an 'end' entry for an asset whose 'begin' entry was never written, so the log's transaction pairing is broken. The whole log is considered invalid and assets are reprocessed from scratch.

Source

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

    /// An error that could not be recovered from. All assets will be reprocessed.
    #[error("Encountered an unrecoverable error. All assets will be reprocessed.")]
    UnrecoverableError,
    /// 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 processed/imported assets folder so the log is recreated
2. Ensure the processor is not killed abruptly between begin and end transactions (graceful shutdown)

When it happens

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