bevyengine/bevy · error · ValidateLogError
Failed to read log entries: {0}
Error message
Failed to read log entries: {0} What it means
ValidateLogError::Io: validating/reading entries of the ProcessorTransactionLog hit an underlying io error (truncated file, unreadable log, etc.). The log cannot be trusted for incremental processing decisions until the io problem is fixed.
Source
Thrown at crates/bevy_asset/src/processor/log.rs:265
/// An error that occurs when writing to the [`ProcessorTransactionLog`] fails.
#[derive(Error, Debug)]
#[error(
"Failed to write {log_entry:?} to the asset processor log. This is not recoverable. {error}"
)]
pub(crate) struct WriteLogError {
pub(crate) log_entry: LogEntry,
pub(crate) error: BevyError,
}
/// An error that occurs when validating the [`ProcessorTransactionLog`] fails.
#[derive(Error, Debug)]
pub enum ValidateLogError {
/// 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
- Check the inner io error and repair filesystem conditions (space, permissions)
- Remove the log file to fall back to full reprocessing
- Prevent concurrent processors from writing the same log
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/bevy_asset/src/processor/log.rs:265 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/70a4ed4af5a95a2c.
Report an issue: GitHub.