Debug Notes
When Scheduled Parameters Override Interactive Defaults
Interactive and scheduled runs can resolve different values from the same execution code path.
Details are generalized and sanitized to preserve confidentiality while keeping the engineering lesson accurate.
Checklist
- Check scheduler-level parameters before code-level defaults.
- Compare parameter values from interactive and scheduled runs.
- Log resolved parameters at runtime.
- Treat deployment configuration as part of the runtime contract.
Why this matters
A common failure mode is that a module passes interactive testing but resolves a different period value in the scheduled workflow. Validate resolved parameters at runtime and fail early on mismatches.