managed path '{}' notifies unconfigured bootstrap service '{

Error message

managed path '{}' notifies unconfigured bootstrap service '{}'

What it means

validate_notifications verifies each notify entry names a bootstrap service that actually exists in configuration. If a managed path notifies a service name that is configured nowhere, mise bails with this error, since the notification could never be delivered.

Source

Thrown at src/system/services_common.rs:311

                .iter()
                .map(move |notification| (file.path.as_path(), notification))
        })
        .chain(directories.iter().flat_map(|directory| {
            directory
                .notify
                .iter()
                .map(move |notification| (directory.path.as_path(), notification))
        }))
    {
        if user_services.iter().any(|name| name == notification) {
            bail!(
                "managed path '{}' notifies user-scope bootstrap service '{}'; notifications apply to system services only",
                resource.display(),
                notification
            );
        }
        if !configured.contains(notification.as_str()) {
            bail!(
                "managed path '{}' notifies unconfigured bootstrap service '{}'",
                resource.display(),
                notification
            );
        }
    }
    Ok(())
}

fn default_true() -> bool {
    true
}

View on GitHub (pinned to afd2eddd3a)

Solutions

Correct the service name in the notify list to match a configured service
Add a `[bootstrap_services.<name>]` declaration for the referenced service
Remove the stale notify entry

Example fix

// before
notify = ["myap"]

// after
notify = ["myapp"]

Defensive patterns

Strategy: validation

Validate before calling

for svc in notify_list {
    if !all_configured_services.contains(svc) {
        eprintln!("notify references unknown service: {svc}");
    }
}

Prevention

Update notify lists whenever a service is renamed or deleted
Use consistent naming between [bootstrap_services.X] blocks and notify entries
Lint config for dangling references in CI

When it happens

Trigger: A managed path's `notify` list contains a service name absent from both system and user bootstrap service declarations.

Common situations: Typos in the service name; renaming or deleting a service without updating notify lists; copying path config from another project with different service names.

Understand the failure class

Background: 'Could not be found', 'does not exist', 'not found in database': the resource-not-found family when an ID, slug, key, or URI lookup comes back empty — this error's family across 20 libraries.

Related errors

AI-assisted analysis of jdx/mise@afd2eddd3a (2026-09-09). Data as JSON: /api/errors/c4aaebf10f356542. Report an issue: GitHub.