Troubleshoot file uploads

Recover the failed transfer before starting another copy. A file that already appears in Library may instead have a separate processing problem.

Recover a failed Library batch

1. Leave CareMap open and wait until the panel has no active or queued files.
2. Review the completed and failed file names.
3. Restore your connection and confirm access to the original destination.
4. Select Retry failed.

This retries only failed selections, using their original folder and upload attempt. It can recover a lost response without intentionally creating another item. Successful files are not resent.

Dismiss clears the settled panel and its retained selections; it does not remove completed files. A new file selection after the batch settles replaces the old batch. Closing or reloading CareMap also loses this local selection.

If the panel is gone, inspect the destination first. Select only files that still need uploading. A newly selected file is a new upload, even if its name matches an existing file.

If upload cannot start

• No upload action: check Owner or Read-write folder access and whether the workspace permits authoring.
• Empty file: choose a nonempty original.
• Too large: Library files allow at most 50 MB each (50,000,000 bytes). A smaller batch does not fix an oversized individual file.
• Insufficient storage: check Settings > Account > Usage, including Usage workspace and uploads in progress. Shared files use their owning workspace's capacity. Organization usage may require authorized Staff access.
• Different uploader: use its displayed limit. Guide/Form packages allow 25 MiB; bulk Person document uploads also have their own 25 MiB limit.

Removing content may take time to change usage, and retained history can still occupy storage. Review allowances or ask an authorized workspace manager for help.

Match the recovery to the state

Uploading is still transferring; wait before selecting the file again. Uploading through server is an automatic fallback, not a second file you need to submit.

An explicitly expired upload attempt needs a new selection of the original. If retry keeps failing, inspect Library for a completed item before dismissing the old batch and starting again.

Processing, Waiting for a processor, or Ready for AI search concerns the stored file's preparation. Use processing recovery for that stage.

If it still fails

Record the platform, destination, filename, approximate size/type, visible status, and time. The batch notification can be generic, so do not assume it identifies the cause. Share relevant details with your administrator or support through an approved channel. Keep private files and temporary download links out of ordinary messages.