bevyengine/bevy · error · ExtractAppDataError

executable schedule has not been created for label "{0}"

Error message

executable schedule has not been created for label "{0}"

What it means

ExtractAppDataError::ScheduleNotInitialized: while extracting schedule data, a schedule with the given label had no executable/initialized schedule (created by Schedule::initialize), so its systems and ordering cannot be inspected. Usually means the schedule never ran or initialize was not called before extraction.

Source

Thrown at crates/bevy_dev_tools/src/schedule_data/serde.rs:472

        let components = component_trace.components;

        Ok(Self {
            name: format!("{:?}", schedule.label()),
            components,
            systems,
            system_sets,
            hierarchy,
            dependency,
            conflicts,
        })
    }
}

/// An error occurring while attempting to extract schedule data from an app.
#[derive(Error, Debug)]
pub enum ExtractAppDataError {
    /// A schedule has not been initialized through [`Schedule::initialize`].
    #[error("executable schedule has not been created for label \"{0}\"")]
    ScheduleNotInitialized(String),
}

#[cfg(test)]
/// Tests for extracted schedule data.
///
/// This is public to allow other test modules in this crate to use its utilities.
pub mod tests {
    use bevy_app::{App, Update};
    use bevy_ecs::{
        component::Component,
        query::{With, Without},
        schedule::{IntoScheduleConfigs, Schedules, SystemSet},
        system::{Commands, Query},
    };
    use bevy_platform::collections::HashMap;

    use crate::schedule_data::serde::{

View on GitHub (pinned to 396ca72708)

Solutions

  1. Run or initialize the schedule (Schedule::initialize / app.update) before extracting data
  2. Verify the schedule label used for extraction matches an initialized schedule
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at crates/bevy_dev_tools/src/schedule_data/serde.rs:472 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/b7a282f324046e9f. Report an issue: GitHub.