When you define a new cloud environment a reservation lockout period begins (default is 48hrs), this is designed to reserve this cloud from someone else taking it for scheduling.
When a cloud environment is released and expires within 48hours this is still active, it'd be nice to have cloud expiration also close the cloud define lockout period too.
e.g. cloud02 was provisioned below for only a few hours and then naturally expired but quads --find-free-cloud returns:
cloud02 (reserved: 43hr 37min remaining)
cloud03 (reserved: 47hr 59min remaining)