This is the change our customers asked for most often, and the reason is commercial rather than technical: an index that nobody refreshes quietly stops being worth paying for.

Almost everything you use BucketPilot for is read from the index — the object counts, the folder sizes, the cost estimates, search, the duplicate report and every size and cost alert threshold. Indexing a bucket was one flow we walked you through; keeping that index fresh was a separate switch, on a different tab, off until somebody found it. Customers who never found it were being shown last month's storage and billed for this month's, and had no way to tell from the screen which one they were looking at.

What changed: the first time a bucket finishes indexing, a daily re-scan is switched on for it automatically. New and changed objects appear, deleted ones drop out, and the figures on every page stay current without anyone remembering to do anything.

And you can turn it off. Any bucket, at any time: open the bucket and use the Auto-sync new objects switch. Off means off — re-index that bucket by hand as many times as you like and it stays off. We only ever choose the default for a bucket's first index, so the setting is never quietly reapplied over a decision you made.

A few things worth knowing:

• •We choose the time, and that is deliberate. Each bucket's re-scan is placed at a quiet moment, with buckets that share one file server kept clear of each other, so a workspace with dozens of buckets doesn't start all of them at once. If you need a particular bucket to run at a specific hour, ask support and we'll pin it.
• •Hourly is still available from the schedule dropdown once auto-sync is on. Daily is the default because it is the cadence that fits every bucket size.
• •Very large buckets stay off. If a full re-scan of a bucket cannot comfortably finish inside a day, we leave auto-sync off rather than start a scan that never catches up. Those buckets belong on daily S3 Inventory indexing instead.
• •Buckets already on S3 Inventory are unaffected — they refresh from their daily manifest, which is what that mode is for.
• •Included from Starter up, on every paying plan. A bucket that has reached your plan's indexed-object limit pauses its re-scans and says so on the bucket, rather than showing a switch that reads "on" while nothing happens.

Buckets you had already indexed before today were switched on as part of this change, with the same rules — including the one that leaves the too-large ones alone.