Account with expired lease not reset

[tysonstewart]

Version information
DCE-CLI 0.5.0 on WSL2/Ubuntu (Windows 10 2004)
(Deployed DCE via CLI 0.5.0 on Amazon Linux 2, most recent Docker image as of bug filing.)

Describe the bug
I am a brand-new user. I have tried to research this as much as I can before filing an issue. The bug is as the title says, and here is the context:

• Two child accounts:
  • One leased for 2 hours with non-admin account
  • One newly-added and in the "NotReady" state
• Newly-added account did not have an alias set, so resetting failed
• Lease expired on other account, but account status is still "Leased" as of 18 hours later
• Logs for update_lease_status Lambda function show leased account expiring as expected
• No other logs show activity for that expired lease account

To Reproduce
Not 100% confident that it will reproduce, but the context given above is my best suggestion.

Expected behavior
Account with expired lease gets reset on first Lambda function run after expiration date, regardless of failure of reset for other accounts.

Additional context
I suspect that the failure of the newly-added account to reset may have interrupted the reset of the expired-lease account. Or perhaps accounts with expired leases are not reset for a period of time after expiration for usage/billing tracking purposes. If it's the latter, then documenting that time would be helpful (apologies if it is and I missed it).

[tysonstewart]

Update: it looks as though this bug was patched in #353. Perhaps I should move the request over to the dce-cli repo?