Expected Behavior
A Schedule whose action carries a VersioningOverride (e.g. a pinned Worker
Deployment Version) should start its workflows with that override applied, the
same way a direct StartWorkflowExecution with the same override does.
This matters for schedules whose workflow input shape changes between builds: the
override is the only way to keep a schedule’s declared input and the code that
receives it on the same Worker Deployment Version.
Actual Behavior
The override is accepted, persisted and readable back via DescribeSchedule, but
it is never applied to the workflows the Schedule starts. The started executions
have no versioning override at all and are routed to the Current version.