backgroundJobs.continueOnIdle is not present in the 2.2.15 schema or runtime. The backgroundJobs schema object is not .strict(), so the key is silently discarded during validation. No warning or error is emitted.
backgroundJobs.orchestratorWake defaults to { "enabled": true, "intervalMs": 300000 }. A configuration carrying continueOnIdle: false therefore runs with periodic wakes enabled, with no indication that the setting was dropped.
Two further observations in 2.2.15:
- The release notes and commit
2c69132 state the default wake interval was raised from 5 to 10 minutes. The shipped schema and runtime both use 300000 ms.
orchestratorWake can start a parent turn via session.promptAsync while child tasks are still running.
Requested:
- Emit a warning for the removed key rather than stripping it silently, or map
continueOnIdle: false to orchestratorWake.enabled: false for one release.
- Correct either the documented or the shipped wake interval default.
Version: 2.2.15
backgroundJobs.continueOnIdleis not present in the 2.2.15 schema or runtime. ThebackgroundJobsschema object is not.strict(), so the key is silently discarded during validation. No warning or error is emitted.backgroundJobs.orchestratorWakedefaults to{ "enabled": true, "intervalMs": 300000 }. A configuration carryingcontinueOnIdle: falsetherefore runs with periodic wakes enabled, with no indication that the setting was dropped.Two further observations in 2.2.15:
2c69132state the default wake interval was raised from 5 to 10 minutes. The shipped schema and runtime both use300000ms.orchestratorWakecan start a parent turn viasession.promptAsyncwhile child tasks are still running.Requested:
continueOnIdle: falsetoorchestratorWake.enabled: falsefor one release.Version: 2.2.15