EventBridge scheduler schedules wrong ECS task definition

The AWS EventBridge Scheduler seemingly schedules the wrong ECS Task Definition. We noticed in the ECS that the tasks spun out via EventBridge is the wrong revision. Following log is from the CloudTrail:

...
"requestParameters": {
        "clientToken": "7929d6d1-048b-4f4a-afbd-2186b2a6b5a3",
        "count": 1,
        "launchType": "FARGATE",
        "networkConfiguration": {
            "awsvpcConfiguration": {
                "assignPublicIp": "DISABLED",
                "securityGroups": [
                    "sg-0334e4fe23d54ef07"
                ],
                "subnets": [
                    "subnet-007eb8e8a5c2a4cbb",
                    "subnet-0c8fcbcbe5c67b8f4"
                ]
            }
        },
        "cluster": "arn:aws:ecs:eu-west-1:xxxxxxxxx:cluster/prod",
        "enableExecuteCommand": false,
        "taskDefinition": "arn:aws:ecs:eu-west-1:xxxxxxxxxxx:task-definition/prod-scheduled-ar:31",
        "startedBy": "chronos-schedule/scheduled-ar",
        "enableECSManagedTags": false
    }
...

Does not correspond to the Terraform/Console configuration for the EventBridge Schedule:

TaskDefinitionArn:
"arn:aws:ecs:eu-west-1:xxxxxxxxxx:task-definition/prod-scheduled-ar:37",
TaskCount:
1,
LaunchType:
"FARGATE",
NetworkConfiguration:
{
awsvpcConfiguration:
{
Subnets:
["subnet-007eb8e8a5c2a4cbb","subnet-0c8fcbcbe5c67b8f4"],
SecurityGroups:
["sg-0334e4fe23d54ef07"],
AssignPublicIp:
"DISABLED"
}
},
PlatformVersion: --

Now we do update the EventBridge schedule every time we create the new revision but it doesn't RUN it when cron executes. I wonder why it is running the older task revisions. Any idea?