Skip to content

Commit b704504

Browse files
authored
Merge pull request #2835 from udmehta/patch-1
Update public docs to explicitly call out org disabled after Copy lifecycle operation failures and possible next steps
2 parents 94b92f9 + ed9b981 commit b704504

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

power-platform/admin/copy-environment.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Copy an environment
33
description: Learn how to copy apps and data from an environment. Review next steps for administrators in the target environment.
44
ms.topic: how-to
5-
ms.date: 2/7/2025
5+
ms.date: 12/04/2025
66
author: ChrisGarty
77
ms.author: cgarty
88
contributors:
@@ -215,6 +215,8 @@ After modifying and enabling some of the plug-ins, the developer sandbox environ
215215

216216
After the copy process is complete, the target environment is placed in [Administration mode](sandbox-environments.md#administration-mode) and background operations are disabled. The next section describes recommended Administrator actions for the newly created copy (target) environment.
217217

218+
The copy process, especially for environments with large amounts of data, is a complex backend operation. If the copy operation fails, the target environment is left in a disabled state. To retry the copy operation, the failed environment must be the target environment for the operation. Wait 30 minutes and retry the operation again. The other actions you can take for the disabled, target environment are reset, delete, or restore.
219+
218220
### How to copy audit logs
219221

220222
Copying audit logs can significantly add to the time it takes to copy an environment and by default isn't done. To include audit logs in the environment copy, perform these steps.

0 commit comments

Comments
 (0)