Apparent Bug in PUT /api/v1/arm/hostpool/{subscriptionId}/{resourceGroup}/{hostPoolName}/auto-scale

I've identified a bug today that you can't currently deploy the auto-healing of broken hosts via the API. Previously, like I wrote in my Blog Article: Deploying Azure Virtual Desktop with Nerdio Manager for Enterprise

You would configure autoHeal like this:

"autoHeal": { "enable": true, "config": { "wvdStatuses": ["Unavailable"], "sessionCriteria": "WithoutActive", "staleHeartbeatMinutes": null, "restartAttempts": 2, "waitMinutes": 10, "finalAction": "DeleteHost" } } }

Looks like that has changed to this syntax:

 "autoHeal":  {
                        "enable":  true,
                        "config":  {
                                    "wvdStatuses":  [
                                    "Unavailable"
                                    ],
                                    "sessionCriteria":  "WithoutActive",
                                    "staleHeartbeatMinutes":  null,
                                    "waitMinutesBeforeFirstAction": 10,
                                    "waitMinutes":  10,
                                    "actions": [
                                     {
          "type": "RestartVm"
        },
        {
          "type": "RestartVm"
        },
        {
          "type": "RemoveVm"
        }
      ]
    }
  }

Both now result in the error:

{ "errorMessage": "Default schedule. Auto-heal: number of recovery actions should be between 1 and 10", "innerMessage": "Auto-heal: number of recovery actions should be between 1 and 10" }