Use the service’s Usage page to compare measured storage with its quota and review history. PD AWS S3’s scheduled readings use CloudWatch daily storage metrics; the measurement timestamp matters as much as the number.

Read the current measurement

Open the intended service and review bytes used, object count, quota, history and the available last-update information. Daily provider data can lag; a newly created bucket or a recent deletion may not yet appear in that reading.

Request a current refresh

1. Open the service’s usage controls and choose Refresh.
2. Read the result rather than repeatedly clicking.
3. If rate-limited, wait for the interval shown.
4. Compare the refreshed measurement, source time and access state.
5. Inspect any remaining discrepancy before changing the quota.

Staff can use Clients & Storage → Collect usage now. Refresh can apply quota policy and send threshold notifications; it is not merely a visual reload.

For a current refresh, this provider attempts a bounded version-aware bucket count. Where that count is incomplete, it can retain a daily provider reading instead of presenting a partial live result as exact. Do not promise an instantaneous complete figure for every bucket size.

Explain stored versions and recovery

Previous versions can continue using space after a visible file is removed. Check the versioning guide before expecting deletion to clear a quota pause. A new valid measurement or intended quota upgrade is needed to reassess access.

Retain the service, measurement time, relevant state and redacted result while your hosting team checks the measurement scope. Avoid full object inventories and customer file contents.

Allow for missing daily metrics

If CloudWatch has no data for a bucket, the module can use a bounded object/version walk as a fallback. That fallback can be accepted even when its listing was incomplete, so a completed Refresh or recent page update is not proof that every object and version was counted. Your hosting team and AWS administrator should compare the intended bucket set and actual storage before relying on an apparent space reduction or treating a quota-related access change as evidence of a complete measurement.

Check the usage sample

Your hosting team should compare the original collection/Refresh time, available source time, bucket scope and Activity result with scheduled CloudWatch figures and the actual storage state. Review normal scheduled work and the named metric-read/listing permission separately; Refresh can apply quota policy and threshold notifications. Check missing daily metrics and bounded fallback coverage before treating a completed result as a full count. Do not send full object inventories or repeat Refresh merely to obtain a different number.

See the PD AWS S3 WHMCS guide for related tasks, or explore the module.