Help Center/ Object Storage Service/ FAQs/ Back to Source/ Why Are Files in the OBS Bucket Not Updated After the Origin Server Files Are Updated?
Updated on 2026-08-20 GMT+08:00

Why Are Files in the OBS Bucket Not Updated After the Origin Server Files Are Updated?

If a file has been pushed by the origin server to an OBS bucket through mirroring, OBS does not simultaneously update the file even if the source file changes. You can use the following methods to indirectly synchronize files in OBS with those on the origin server:
  • Manually deleting retrieved files: Manually delete the files cached in the bucket using the console or APIs. This ensures that the system fetches the latest data from the origin server on the next pull.
  • Configuring lifecycle rules to periodically delete retrieved files: Configure lifecycle rules for retrieved files so that they are automatically deleted after a specified period. This ensures that the system fetches the latest data from the origin server on the next pull.
  • Naming origin server files by version: When origin server files are updated, use version names or timestamps (for example, testv1.txt or test20260617181156.txt) to distinguish them. This helps quickly identify updated files.