VMs are deallocated and deleted too early

I've been working on a POC with Azure CycleCloud and HPC Pack 2019. From the head node, the auto-scaling configuration looks like this:

```
{
"archivefile": "C:\\cycle\\jetpack\\config\\autoscaler_archive.txt",
"boot_timeout": 1500,
"cluster_name": "TEST-HPC",
"default_resources": [],
"disable_default_resources": false,
"idle_timeout": 900,
"lock_file": "C:\\cycle\\jetpack\\config\\scalelib.lock",
"password": "*********",
"statefile": "C:\\cycle\\jetpack\\config\\autoscaler_state.txt",
"url": "https://172.17.10.4:9443",
"username": "cyclecloud_access",
"autoscale": {
"start_enabled": true,
"vm_retention_days": 7
},
"hpcpack": {
"hn_hostname": "localhost",
"pem": "C:\\cycle\\jetpack\\config\\hpc-comm.pem"
},
"logging": {
"config_file": "C:\\cycle\\jetpack\\config\\autoscale_logging.conf"
},
"pbspro": {
"read_only_resources": [
"host",
"vnode"
]
}
}
```

However, when I start a new job, which starts a new node, what I see is:

* The VM is deallocated after around 5 minutes, regardless of when the last job finished (once it started deallocating less than 30 seconds after finishing the last job).
* The VM is deleted a matter of minutes after being deallocated (don't have an exact amount of time, but less than 30 minutes), even when the configuration says 7 days.

What am I doing wrong, or what could be wrongly configured, that would result in this situation?