Your overseas designer is ready to adapt a product campaign, but the download address supplied by the production partner no longer opens. Has the master been deleted, has permission changed, or has only the address expired? Those possibilities require different responses.
For a brand working with a China-based studio or AI content supplier, ONCE recommends three separate clocks for delivery: access, retention and agreed usage. A sent link does not settle all three. This article uses a hypothetical handoff, not a client incident or a completed ONCE test.
Start with the access mechanism
Amazon S3’s presigned URL documentation, checked November 8, 2026, explains that links provide time-limited access. A URL created with temporary credentials expires when those credentials expire, even if its configured deadline is later. In that system, access failure can therefore arise without establishing that the object was deleted.
Scenario’s current Content Delivery Network documentation, checked the same day, says asset URLs other than thumbnails are signed and expire automatically. That describes one service’s delivery mechanism. It does not establish universal AI-platform expiry periods or promise indefinite retention. No publication date was established for either page; these are current references for an evergreen procurement issue.
The operational response is to check the asset, its revision and the recipient’s authorization before issuing another access route. Do not presume that a failed address means a production failure. Equally, do not promise that the original must still exist.
Give each clock an owner
Access: record when this download route ends, what recipient verification is required and how a replacement route can be requested. Use an explicit date, time and timezone across the international handoff. The technical team should also account for credentials or policies that can shorten effective access.
Retention: specify which files are held, where, by whom and until when. Agree the process for extending storage or transferring the archive. Finished masters, selected footage, generated outputs and editable projects can have different retention commitments. A lasting gallery address does not establish that every source file is included.
Agreed usage: keep the approved channels, territories, periods and other conditions with the asset record. A working download is not evidence that every underlying usage term has been extended. An expired address also does not, by itself, determine the status of the agreement. Refer questions about scope to the relevant project documentation and authorized decision-maker.
These clocks can differ. A supplier might keep a master under an agreed retention term while issuing short access windows for individual recipients. An available file might still need a new-channel usage check. These are service-design examples, not default contract terms or legal conclusions.
Recover the approved version before commissioning a replacement
ONCE proposes an asset record containing the project and asset identifier, approved revision, filename and format, size, a checksum where appropriate, custodian, agreed usage conditions and current delivery route. The temporary URL is one field in that record, rather than the sole identity of the work.
For a resend, locate the specified revision and confirm that it is readable and authorized for the recipient. If it remains available, provide access to that version. If it has been removed, report that accurately and discuss the options. Do not silently substitute another file. An identifier alone does not establish unchanged content; verify the revision and file as well.
With AI assets, downloading an original result and generating a similar-looking replacement are different services. A newly generated file requires renewed checks for product shape, text, movement and approval. An expired URL does not justify treating a new output as the previously approved asset.
For related production and archive planning, see ONCE’s video production insights. The question here is the handoff itself: which version should be recovered, who may receive it and what confirms that it has reached the recipient’s working environment?
Verify receipt, then test the resend process
Use a mutually agreed test asset. Have the recipient retrieve it on an authorized device and network, compare it with the delivery manifest, open it and confirm storage in the agreed destination. Until that happens, mark receipt as pending. An email sent or a link clicked does not establish file acceptance.
A recurring service can also include a resend exercise after the original test address naturally expires. Request the asset by identifier and verify the returned file against the original record. This is a suggested acceptance method, not a test ONCE has performed, and it does not require disrupting live business links.
A durable client portal can provide a stable place to find an asset while generating temporary download routes behind it. Stable discovery need not mean permanently public files. Define who can search and download, and how files are exported or transferred when the relationship ends.
Price ongoing availability as a defined service
Separate agreed storage, catalog and permission maintenance, resends and transfer, receipt verification, and any actual repair or new production. Identify what is included in the project or retainer. Do not charge a fresh generation merely because a link failed before investigating it; equally, do not leave out-of-scope recovery under an unlimited free-storage promise.
For ONCE’s long-term move toward managed content services, the reusable operating asset is an authorized catalog of approved revisions and responsibilities, rather than a collection of temporary URLs. Whether those records improve margin depends on actual service effort and cost; no savings percentage is asserted here.
At the next handoff, request three explicit answers: when access ends, what retention covers, and which usage conditions have been confirmed. Assign a recipient as well. Those decisions turn an expired link into a defined recovery task instead of a new production brief.
