Carry unresolved reservations across the UTC month boundary

A calendar reset does not cancel an external effect

A monthly budget is a policy window for new admission. It is not a command to forget work whose provider outcome remains unresolved. If a request may already have been accepted before midnight, clearing its reservation would make the next month’s available headroom look larger without removing the possible charge.

Lupin’s provider-cost limits reset by UTC calendar month while outstanding reservations from earlier months continue counting until resolved. Read that behavior as a safety invariant. A new month can have little newly settled activity and still have substantial committed capacity tied to older operations.

Distinguish spent from reserved

The budget view separates settled spend and reserved estimates. Inspect their timestamps and statuses rather than reading one combined progress bar as all newly incurred cost. An old reservation can represent a lost response, an unfinished runtime or a provider acceptance whose local projection could not be completed.

Deleting a resource or project does not erase permanent usage history. A cleanup action may help stop future runtime, but it does not prove that a prior operation never happened. Keep the original event and attribution available for reconciliation even when its user-facing resource is no longer active.

Investigate the unresolved set

Group open reservations by product, age, operation reference and last known phase. Prioritize cases with a known provider outcome that can complete local recovery, then distinguish definite rejections from genuinely unknown requests. Age alone does not authorize releasing an entry.

For running resources, inspect termination evidence and the documented runtime quantity basis. Lupin notes that runtime observations can be upper bounds when exact provider termination time is unavailable. Record that limitation instead of inventing a precise stop timestamp from the moment an operator opened the incident.

Keep retail cycles separate

The customer retail metering cycle may follow subscription state, while provider-cost budgets use UTC months. A reservation that matters to a budget can therefore appear under a different period boundary than an invoice preview. Align each report’s timestamps and accounting basis before treating the difference as a defect.

Outstanding retail settlement or export can also delay invoice readiness. Do not move old activity into a newer period simply to close a report. Preserve the original cycle and use the supported reconciliation path so the resulting accounting explains when the activity was admitted and what remained uncertain.

Close old reservations with evidence

Provider acceptance allows appropriate settlement; authoritative rejection allows release. A missing provider view or elapsed client timeout does neither. When evidence remains unavailable, leave the reservation visible and assign an owner for escalation. Disabling a budget can change future admission, but it is not reconciliation of its prior history.

For operations reviews, track age buckets and resolution reasons alongside the monetary total. A growing unresolved set can reveal storage failures, missing callbacks or incomplete cleanup even when current-month traffic is low. Fixing those causes restores usable headroom through accurate state, rather than through an arbitrary calendar reset.

Sources & verification

Reviewed against the checked-in Lupin implementation and official reference documentation on 2026-11-05. Operational examples are illustrative; no live paid action, provider mutation or external message was executed.

• Lupin usage ledger and spending limits ↗Checked 2026-11-05
• Lupin billing, metering and retained storage ↗Checked 2026-11-05

Prepared with AI assistance by Lupin editorial. How we research and maintain these guides.