Use the unmatched-resource queue to investigate possible wasted spend. Its title is a review prompt, not evidence that a resource should be deleted.

Review the queue

1. Open PD Modules → Cost & Margin → Paying for nothing.
2. Choose the intended month and Things to look at.
3. Review the resource, provider, type, region, cost and displayed age.
4. Check the underlying bill and resource ownership before making any operational decision.

The age comes from when the module first stored that provider-resource-month row. It is not proof of the resource’s creation date or the first day the provider began billing. A new month or a late import can therefore start a new waiting period for an older resource.

Review the thresholds

In Settings, review Days before an unmatched resource counts as an orphan and Ignore orphans costing less than this a month. Changing those settings changes which stored rows qualify; it does not change provider spend or establish ownership.

The released queue limits candidates before applying its age and cost tests. Older qualifying rows can be outside that candidate set, and an empty view is not proof that every unmatched charge is harmless. Check provider counts and coverage as well as the visible queue.

Check what the row represents

An expected shared resource, backup or aggregate service-level charge may have no matched customer service. Some rows can be a provider service total rather than a separately deletable resource. Incomplete name matching can also put legitimate customer resources here.

Use Expected only after reviewing the reason. Any actual resource shutdown requires your normal authorised operational workflow and independent dependency review. The Cost & Margin queue itself does not delete resources at the provider.

See the PD Cloud Cost & Margin Blesta guide for related tasks, or explore PD Cloud Cost & Margin.