The key idea
Verify the delivery manifest, receipt, processing result, review decision and final asset identifier. An upload reaching 100% describes transfer progress; the receiving team must still confirm processing, review and asset readiness before publication.
Agree on the delivery manifest first
Record the project, market, language, asset version, filename, expected count, destination folder and recipient. Use the current receiving page and intended placement requirements for dimensions, duration, formats and size limits. A limit observed in one workflow is not a universal account policy.
Keep distinguishable versions when captions, visuals, audio or end cards change. Retain originals and revision notes until acceptance. Identical filenames can contain different edits and do not prove that the current delivery already exists.
- Use the current link provided by the receiving team.
- Check that each source file opens or plays locally.
- Associate every file with its language, version and destination folder.
Separate transfer, receipt, processing, review and readiness
Transfer means the browser is sending files. Receipt means the service has a corresponding task or file record. Processing may include import and file checks. Review determines acceptance under the delivery requirements. Readiness should be confirmed against the correct object in the receiving library. Labels vary between upload flows; verify their actual meaning.
VeeMetr’s external creative workspace distinguishes processing, pending review and exception states. Availability depends on deployment configuration and permissions. External assets subject to review cannot be used in ads before approval. Library acceptance does not establish ad-platform approval or live delivery.
The recipient should open the final asset, check visuals, captions, version and folder, and record its identifier. A delivered notification or a chat acknowledgment is not a substitute for that check.
Worked example: reconcile three different outcomes
This is a workflow example, not a customer record. The manifest contains clip_en_v01, clip_en_v02 and clip_zh_v01. The first is ready in the library, the second awaits review, and the third cannot be parsed.
Record one ready asset, one pending review and one requiring repair, each with its task or asset identifier. The reviewer handles the second file; the editor checks and re-exports the third. Preserve the first object instead of uploading it again because the whole batch is incomplete.
Before closing delivery, record a final disposition for every file. Keep approval, rejection, withdrawal and pending work distinct. The delivered count is not the approved count.
Choose recovery based on the failure
For an invalid link, ask the recipient to verify the current link before sending again. For an interrupted connection, preserve the files and task context and use the page’s continuation or retry action. If processing is still underway, inspect progress and update time before creating a duplicate task.
The current VeeMetr workspace presents different guidance for failed imports, conflicting names and invalid files. Retry imports when offered; reconcile an existing version before renaming; follow the available recheck or re-export guidance for unparseable files. Rechecking also depends on retention of the original file.
For size or integrity mismatches, check the source and follow the re-upload guidance. After recovery, confirm the final library object. Clicking retry is not evidence of resolution.
- Retain the task identifier, failure time and displayed reason.
- Reconcile successful items before submitting again.
- Share only necessary diagnostic information; do not publish complete upload links or credentials.
Close the delivery and review future access
Link management is separate from asset acceptance. In the current workspace, disabling a contributor prevents new uploads while received assets continue processing. Issuing a replacement link can invalidate the previous link immediately. Check outstanding uploads before changing access.
Pass the final asset identifier, version, review decision and usage constraints to the publishing team. Copy, destinations, target accounts and platform requirements still need publication checks. Receiving-team approval does not replace ad delivery verification.
Frequently asked questions
Why can I not select an asset when its upload is at 100%?
The percentage usually describes transfer progress. The recipient must still confirm processing, review and readiness against the correct asset object and its current state.
Should I upload the whole batch again after some files fail?
Reconcile successful, pending and failed files first. Preserve confirmed objects, recover only unfinished items according to the cause, and verify them afterward.
Does disabling an upload link delete received assets?
The current workspace’s disabling action prevents subsequent uploads; it is not deletion of received assets. Task cancellation, temporary-file cleanup and asset deletion have separate behavior.
Is VeeMetr external creative collaboration enabled for every account?
No. The workspace requires deployment configuration and permissions. Available entry points, file support and actions depend on the current account setup.