Revoking leases that have reached maximum revoke attempts

The amount of revocation attempts (6) is hardcoded in the Vault source code and is not configurable anywhere it seems. Once this limit is reached (e.g. with database secrets due to a temporary database outage), these leases will stay indefinitely.
What is the recommended procedure for cleaning these up after the fact automatically?

I tried the /sys/leases/tidy endpoint, but this does not clean up expired leases that are not corrupt. It looks like there is not a simple way of listing and revoking all leases that have expired a while ago but are still there, so how do I automate this?

Allright, when I restarted Vault it actually revoked all old leases. For now just restarting it regularly will be fine for me, but maybe this could be done automatically in some way.