Significant-Gravitas/AutoGPT · error · ValueError
Transfer has already been executed
Error message
Transfer has already been executed
What it means
Error "Transfer has already been executed" thrown in Significant-Gravitas/AutoGPT.
Source
Thrown at autogpt_platform/backend/backend/api/features/transfers/db.py:173
Requires both source and target approvals, and the caller's active org
must be a party to the transfer — TRANSFER_RESOURCES is granted to every
personal-org owner, so without this check any authenticated user could
execute an approved transfer between two unrelated orgs.
"""
tr = await prisma.transferrequest.find_unique(where={"id": transfer_id})
if tr is None:
raise NotFoundError(f"Transfer request {transfer_id} not found")
if org_id not in (tr.sourceOrganizationId, tr.targetOrganizationId):
raise ValueError("Your organization is not a party to this transfer request")
if tr.sourceApprovedByUserId is None or tr.targetApprovedByUserId is None:
raise ValueError(
"Transfer requires approval from both source and target organizations"
)
if tr.status == "COMPLETED":
raise ValueError("Transfer has already been executed")
if tr.status == "REJECTED":
raise ValueError("Cannot execute a rejected transfer")
await _move_resource(
resource_type=tr.resourceType,
resource_id=tr.resourceId,
target_org_id=tr.targetOrganizationId,
)
now = datetime.now(timezone.utc)
updated = await prisma.transferrequest.update(
where={"id": transfer_id},
data={"status": "COMPLETED", "completedAt": now},
)
await _create_audit_logs(
transfer=updated,View on GitHub (pinned to 9c8bb5550f)
Solutions
- No action needed; the transfer is already executed.
- Refresh the transfer status.
When it happens
Trigger: Thrown at autogpt_platform/backend/backend/api/features/transfers/db.py:173 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Significant-Gravitas/AutoGPT@9c8bb5550f (2026-08-14).
Data as JSON: /api/errors/7bd8484474cd7f9e.
Report an issue: GitHub.