S3 object missing after upload
The product wrote to S3 (or an S3-compatible CDN bucket), then verified with HeadObject and the object was not there.
Why this happens
writeStorageObject finishes the multipart upload, then checks the key. Missing object usually means wrong bucket/region/endpoint, IAM missing s3:HeadObject, credential mismatch, or a rare consistency/path issue. Common on remote URL or other flows that land on a CDN/S3 storage server.
Diagnose and fix
1. Admin → Servers → that CDN/S3 node: bucket, region, endpoint, access key/secret — run test connection.
2. IAM: allow PutObject and HeadObject (and multipart APIs) on the upload prefix.
3. Confirm the file’s assigned server is the node you edited (not a different offline bucket).
4. Check provider logs for failed PUT/Head on that key.
5. See CDN credentials and test connection / CDN custom domain / public URL for setup detail.