---
id: "bug-1964"
status: "open"
status_updated: "2026-10-10"
status_note: "newly logged"
component: "scheduler"
severity: "wrong-result"
timestamp: "2026-10-10T10:16:12Z"
last_seen: "2026-10-10T10:16:12Z"
occurrences: 1
files: ["src/scheduler/src/sim_limit.c", "src/scheduler/src/core_events.c"]
tags: ["scheduler", "sim", "equivalence", "limit"]
related: ["bug-1943"]
gitea_issue: 395
gitea_synced_status: "open"
gitea_synced_hash: "40588533d766"
---

# bug-1964: xce_scheduler --sim does not re-seed limits when a config push arrives mid-replay

## Description
**Observed:** (source reading; follow-up of the 2026-10-10 P0 fixes (bug-1936..1957))
Reported by the bug-1943 fix: the simulator seeds the limit plugin only at bootstrap (`sim_bootstrap_limit_plugin`); a CONFIG_PUSH during replay updates groups (bug-1943) but a new or changed limit config never reaches the limit plugin, while the live scheduler applies it (`plugin_config_update`).

**Expected:** Live and simulated scheduling apply the same limits after a config change.
**Impact:** Replays that span a limit config change decide differently than live.
**Found by:** follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)
## Environment
- OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
- libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
- Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
- Build: asan (xce.build)
- Code: scheduler-framework @ 19be145d-dirty
- Deployment: any (found by source reading; confirmed by the RED test of the fix)

## Reproduction
1. Replay a recording with a CONFIG_PUSH that changes a limit; compare decisions with live.
- Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
- Evidence: the code sites quoted in Description; no logs kept.
## Root cause
TODO: required for fixed/partial

## Fix
TODO: required for fixed/partial

## Verification
- Test: TODO: name + file; RED before the fix, GREEN after
- Suites: TODO: suite results and build profile
- Live: TODO: soak/deploy run, or n/a and why

## References
- Related: none