'Cannot upload, survivor already uploaded' or 'a character is already transferring in the cloud'

The short answer is in Troubleshooting: connection timeout, server full, missing character: do not retry in a loop, message an admin. This page explains why.

"Cannot upload, survivor already uploaded" while you are standing on the map.
ASA: travel is refused with "cannot transfer as there is already a character transferring in the cloud" (reported to Studio Wildcard's tracker as ASAIR-455 and ASAIR-438).
ASA: "character already in upload" stays for more than 24 hours and through several server saves (ASAIR-443).
The message may point you to another server, the one your character is supposedly transferring to.

The short answer is in Troubleshooting: connection timeout, server full, missing character: do not retry in a loop, message an admin. This page explains why.

"Cannot upload, survivor already uploaded" while you are standing on the map.
ASA: travel is refused with "cannot transfer as there is already a character transferring in the cloud" (reported to Studio Wildcard's tracker as ASAIR-455 and ASAIR-438).
ASA: "character already in upload" stays for more than 24 hours and through several server saves (ASAIR-443).
The message may point you to another server, the one your character is supposedly transferring to.

An earlier transfer never completed. The game thinks your survivor is still in the transfer cloud — on our servers that is your account's transfer file in the cluster folder — while the same survivor also stands on the map.

In the reported official cases, a server rollback had put the character back on the map while the cloud copy was still "transferring" (ASAIR-438). The tracker's answer for official servers: transfer your character to the server the message names and wait for a server save, or delete one of the duplicated characters.

On our cluster the rule is different. Two copies of one survivor can each hold the same gear, so an admin decides which copy is the current one, and the stale copy is never downloaded anywhere — that would duplicate the gear.

Do not retry the transfer in a loop, and do not download a copy on another map.
Do not delete one of your characters, even though the official tracker suggests it for official servers. Here the admin compares the copies first.
Message an admin with the two maps involved and the time.
Stay out of the game on that account while the admin works on it: the stale copy is set aside while you are offline.

There is nothing to wait out: one player reported the message lasting more than 24 hours (ASAIR-443).

Always — on this cluster a player cannot clear this message safely alone. An admin:

compares which copy is newer, using the server logs, your sessions and the content of the transfer file;
with the owner's approval and with you offline, sets the stale cloud copy aside — it is kept, not deleted — so it can never be downloaded twice;
if a copy turns out to be damaged, can read an older save with Restore from backup. Whether anything is replaced is the owner's decision.

Tell an admin the map, the time (the clock in your profile menu shows the server's time), your character's name, what you carried or had uploaded, and the exact message on the screen. For a transfer: both maps and both times. Report the same day — the backups reach back only about two days. Contact admin is in your profile menu; the Guides page has a question box.

ASA Account ID, if the admin asks for it: start a single-player game, open the console, type whoami and copy the "OSS Id" (official article What is an Account ID?). It is a plain console command, not a cheat.

Avoid transferring right after a crash or a rollback: the official case shows how a rollback leaves a copy "transferring" in the cloud (ASAIR-438).
If a transfer looks stuck, stop and ask instead of trying again.

ASAIR-438: cannot transfer, a character is transferring in the cloud — official ASA bug tracker, with the tracker's reply
ASAIR-443: Unable to transfer off of server — official ASA bug tracker, user report
ASAIR-455: already a character transferring in the cloud — official ASA bug tracker, user report
Official support: What is an Account ID?
Our guide: Troubleshooting: connection timeout, server full, missing character
Our records: docs/OPERATIONS.md §18 (uploads follow the account's transfer file), docs/SYSTEM.md §12 (Restore from backup); operator notes on the "already uploaded" handling, 08/10/2026

'Cannot upload, survivor already uploaded' or 'a character is already transferring in the cloud'

What you see

Related guides

'Cannot upload, survivor already uploaded' or 'a character is already transferring in the cloud'

What you see

Related guides

Why it happens

What you can do

When to ask an admin

Avoid it next time

Sources