# Cloud Errors

This document compiles a comprehensive list of common error codes during website operations, deployment, infrastructure management, and environment setup processes.

Each error code is accompanied by a clear description of the issue it represents and an extended explanation to aid in diagnosing and resolving the underlying problems.

### Website Operations Errors

<table><thead><tr><th width="228">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>MoveWebsitePreflightStatusCheckFailed{StatusCode}{StatusCodeName}</strong></td><td>Unable to ping website before moving website to server.</td><td>This error occurs when the system fails to ping the website before migrating to a new server. It suggests potential network issues or server unavailability. Retry the operation after verifying network connectivity and server status.</td></tr><tr><td><strong>MoveWebsitePreflightStatusCheckFailedTimout</strong></td><td>Unable to ping website before moving website to server.</td><td>This error occurs when the system fails to ping the website before migrating to a new server. It suggests potential network issues or server unavailability. Retry the operation after verifying network connectivity and server status.</td></tr><tr><td><strong>MoveWebsitePreflightStatusCheckFailedDNSMisconfigured</strong></td><td>Unable to ping website before moving website to server. DNS Misconfigured. Please revisit your website's hostname configuration.</td><td>This error occurs when DNS settings for the website's hostname are misconfigured, preventing successful pinging. Verify DNS configurations and retry the migration after correcting any issues.</td></tr><tr><td><strong>MoveWebsitePostStatusCheckFailed{StatusCode}{StatusCodeName}</strong></td><td>After moving your website to new hardware, we pinged your website and did not retrieve a successful response code. Please review the attached Umbraco Logs and review the redirect rules.</td><td>This error occurs after migrating the website to new hardware, where subsequent checks fail to retrieve a successful response from the website. It suggests potential issues with configuration, redirects, or server settings. Review logs and configuration details, and retry after addressing identified issues.</td></tr><tr><td><strong>MoveWebsitePostflightStatusCheckFailedTimout</strong></td><td>After moving your website to new hardware, we tried to connect to your website, but we were unable to get a response promptly. Please review your website's boot-up performance.</td><td>This error occurs after migrating the website to new hardware, where subsequent checks fail to retrieve a successful response from the website. It suggests potential issues with configuration, redirects, or server settings. Review logs and configuration details, and retry after addressing identified issues.</td></tr><tr><td><strong>MoveWebsitePostStatusCheckFailedDNSMisconfigured</strong></td><td>Unable to ping website after moving website to server. DNS Misconfigured. Please revisit your website's hostname configuration.</td><td>This error occurs when DNS settings for the website's hostname are misconfigured after migration, preventing successful pinging. Verify DNS configurations and retry after correcting any issues.</td></tr></tbody></table>

### Job Monitoring and Execution Errors

<table><thead><tr><th width="260">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>MoveWebsiteJobMonitorFailed</strong></td><td>The component orchestrating the job of moving the website to new hardware failed to get the latest status. An internal error causes this and can safely be retried.</td><td>This error indicates a failure in retrieving the latest status of the website migration job due to an internal issue. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>MoveWebsiteJobTimedOut</strong></td><td>The component orchestrating the job for moving the website to new hardware timed out. This error is typically caused by the repository folder being too large. Please review your repository and try again.</td><td>This error occurs when the job orchestrating the website migration times out due to large repository sizes. Review repository size, optimize content, and retry the migration.</td></tr><tr><td><strong>MoveWebsiteJobFailedToStart</strong></td><td>The component orchestrating the job of moving the website to new hardware failed to start. An internal error causes this and can safely be retried.</td><td>This error indicates a failure in starting the job orchestrating the website migration due to an internal issue. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>MoveWebsiteJobFailedUnhandledError</strong></td><td>The component orchestrating the job of moving the website to new hardware failed with an unhandled error. An internal error causes this and can safely be retried.</td><td>This error indicates a failure in the job orchestrating the website migration due to an unexpected and unhandled error. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>MoveWebsiteUnhandledJobException</strong></td><td>An unhandled exception occurred inside the website migration job. An internal error causes this and can safely be retried.</td><td>This error indicates that the website migration job exited with an unhandled exception. Retry the operation as it may resolve with subsequent attempts. If the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteCloneRepositoryFailed</strong></td><td>The website migration job failed to clone the source repository.</td><td>This error occurs when the migration job is unable to clone the Git repository from the source environment. This may be caused by network issues, repository corruption, or temporary unavailability of the source environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteCheckoutHeadBranchFailed</strong></td><td>The website migration job failed to checkout the head branch of the source repository.</td><td>This error occurs when the migration job is unable to checkout the head branch after cloning the source repository. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteSetRemoteOriginFailed</strong></td><td>The website migration job failed to configure the target Git remote.</td><td>This error occurs when the migration job is unable to configure the target Git remote for pushing the repository. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsitePushToTargetFailed</strong></td><td>The website migration job failed to push the repository to the target.</td><td>This error occurs when the migration job is unable to push the repository contents to the target environment. This may be caused by network issues or temporary unavailability of the target environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteKuduDeploymentFailed</strong></td><td>The deployment to the target environment did not complete successfully.</td><td>This error occurs when the Kudu deployment on the target environment fails to complete. Review the deployment logs attached to the activity for detailed error messages, then retry the operation.</td></tr><tr><td><strong>MoveWebsiteCopyFoldersFailed</strong></td><td>The website migration job failed to copy application folders to the target environment.</td><td>This error occurs when the migration job is unable to copy folders such as App_Code, App_Data, App_Plugins, css, or bin to the target environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteCopyFilesFailed</strong></td><td>The website migration job failed to copy application files to the target environment.</td><td>This error occurs when the migration job is unable to copy required files to the target environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWebsiteCopyDataProtectionFolderFailed</strong></td><td>The website migration job failed to copy data protection files to the target environment.</td><td>This error occurs when the migration job is unable to copy the data protection folder contents to the target environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr></tbody></table>

### Infrastructure and Configuration Errors

<table><thead><tr><th width="259">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>MoveWebsiteFailedUnableToCreateAppService</strong></td><td>We were unable to allocate new hardware for the requests. An internal error causes this and can safely be retried.</td><td>This error occurs when the system fails to allocate new hardware resources for website migration due to internal issues. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>MoveWebsiteFailedUnableToAttachSecretKeyStore</strong></td><td>We were unable to reliably connect the project's secret key store to the new infrastructure. An internal error causes this and can safely be retried.</td><td>This error occurs when the system fails to establish a reliable connection between the project's secret key store and the new infrastructure during migration. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>MoveWebsiteFailedUnableToFetchDeploymentConfiguration</strong></td><td>We are unable to fetch the deployment configuration from our hosting provider.</td><td>This error occurs when the system cannot retrieve the deployment configuration required for migration from the hosting provider. Verify credentials, permissions, or connectivity settings and retry the operation.</td></tr><tr><td><strong>UnhandledExceptionWhileExecutingConfigurationStep</strong></td><td>While updating relations between your environments, we experienced an unhandled exception. An internal error causes this and can safely be retried.</td><td>This error indicates an unhandled exception occurred during updates between environments, suggesting an internal issue. Retry the operation as it may resolve with subsequent attempts.</td></tr><tr><td><strong>CopySharedAppSettingsFailed</strong></td><td>An unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.</td><td>This error indicates a failure while copying shared application settings or secrets from one environment to another during migration. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>CopySharedAppSettingsFailedUnhandledException</strong></td><td>An unexpected error occurred while trying to copy shared secrets from the source environment to the new environment. Please try again, and if the problem persists, please reach out to support.</td><td>Similar to the previous error, indicating an unexpected and unhandled exception during the process of copying shared secrets. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>CopySharedAppSettingsFailedTimeoutExceeded</strong></td><td>The process of copying shared secrets from the source environment to the new environment took longer than expected. Please try again, and if the problem persists, please reach out to support.</td><td>This error occurs when the time taken to transfer shared secrets exceeds the expected duration. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>InitializingGitRepositoryFailed</strong></td><td>An error occurred while trying to configure new hardware. Please try again, and if the problem persists, please reach out to support.</td><td>This error indicates a failure during the initialization of a Git repository on new hardware. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>UpdateRemoteFailed</strong></td><td>We failed to update the Git remotes to adjacent environments. Please try again, and if the problem persists, please reach out to support.</td><td>This error occurs when the system encounters a problem while updating Git remote configurations between environments. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>UpdateDeployConfigFailed</strong></td><td>We failed to update the deploy configuration on your website. Please try again, and if the problem persists, please reach out to support.</td><td>This error indicates a failure to update deployment configuration settings on the website. Retry the operation and contact support if the issue persists.</td></tr><tr><td><strong>FetchFromRemoteFailed</strong></td><td>We failed to fetch changes from an upstream environment. This is most likely caused by the source repository having lots of changes.</td><td>This error occurs when the system encounters difficulties fetching changes from a remote repository due to a large volume of changes. Retry the operation and review repository settings.</td></tr><tr><td><strong>MergeFromRemoteFailed</strong></td><td>We failed to merge changes from an upstream environment. This is most likely caused by the two environments having Git conflicts. Please read <a href="https://docs.umbraco.com/umbraco-cloud/troubleshooting/deployments/structure-error">Umbraco Cloud Git Conflict Resolution</a> on how to resolve Git conflicts on Umbraco Cloud.</td><td>This error occurs when merging changes from a remote environment fails due to Git conflicts. Follow the documentation for resolving Git conflicts specific to Umbraco Cloud environments.</td></tr><tr><td><strong>SetRemoteAsTrackingFailed</strong></td><td>Unhandled error. Please reach out to support.</td><td>This error suggests an unhandled error occurred while attempting to set a remote repository as tracking for changes. Contact support for assistance in diagnosing and resolving the issue.</td></tr><tr><td><strong>BuildAndDeployFailedUnhandledError</strong></td><td>An unhandled exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.</td><td>This error indicates an unexpected and unhandled exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.</td></tr><tr><td><strong>BuildAndDeployFailed</strong></td><td>An exception happened while trying to build and deploy your cloud repository to the website. Please review the Kudu logs and try again.</td><td>This error indicates an exception occurred during the build and deployment process of the website's cloud repository. Review Kudu logs for detailed error messages and retry the operation.</td></tr><tr><td><strong>PlaceSqlInitializeFileFailed</strong></td><td>Unhandled error. Please reach out to support.</td><td>This error indicates an unhandled error occurred while attempting to place an SQL initialization file. Contact support for assistance in diagnosing and resolving the issue.</td></tr><tr><td><strong>PingWebsiteFailed</strong></td><td>We were unable to contact your website and get a successful response. This can be caused by multiple issues such as slow boot-up times, invalid redirect rules, or missing configuration.</td><td>This error occurs when attempts to contact the website fail to retrieve a successful response. Verify website settings, boot-up performance, redirects, and configuration. Retry after addressing identified issues.</td></tr><tr><td><strong>DeployExtractionFailed</strong></td><td>Umbraco Deploy tried to extract changes but encountered a problem. Please review the CMS log files for detailed information.</td><td>This error occurs when Umbraco Deploy encounters difficulties while extracting changes during deployment. Review CMS log files for detailed error messages and take corrective actions as necessary.</td></tr></tbody></table>

### Website Provisioning Errors

<table><thead><tr><th width="263">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>CreateAppPlanFailedUnableToStartProvisioning</strong></td><td>We tried to provision new infrastructure. Our hosting provider was not able to accommodate the request at that time. Please try again.</td><td>This error occurs when the hosting provider fails to provision the new infrastructure as requested. Retry the operation after some time or contact support for further assistance.</td></tr><tr><td><strong>CreateAppPlanFailedUnableToScaleToMatchRequirements</strong></td><td>We retrieved an internal error while trying to scale the requested infrastructure. Please try again.</td><td>This error occurs when scaling infrastructure to meet requirements fails due to an internal error. Retry the operation after some time or contact support for further assistance.</td></tr><tr><td><strong>CreateAppPlanFailedUnableScaleToRequirementTimedOut</strong></td><td>The operation to scale infrastructure to your requirements took longer than anticipated. Please try again.</td><td>This error occurs when the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.</td></tr><tr><td><strong>CreateAppPlanFailedScaleOperationTimedOut</strong></td><td>The operation to scale infrastructure to your requirements took longer than anticipated. Please try again.</td><td>Similar to the previous error, indicating the operation to scale infrastructure exceeds the expected time limit. Retry the operation after some time or contact support for further assistance.</td></tr><tr><td><strong>CreateAppPlanFailedUnhandledError</strong></td><td>An internal error happened while modifying infrastructure. Please try again or reach out to support.</td><td>This error indicates an internal error occurred while modifying infrastructure settings. Retry the operation after some time or contact support for further assistance.</td></tr><tr><td><strong>AppServicePlanChangeUnsupportedOperation</strong></td><td>The requested infrastructure change is not supported.</td><td>This error occurs when an unsupported change is requested for the underlying hosting infrastructure. Please reach out to support for further assistance.</td></tr><tr><td><strong>DedicatedPlanCreatedButNotNeeded</strong></td><td>New hardware was provisioned but is no longer required.</td><td>This error indicates that new infrastructure was provisioned but is not needed for the resulting setup. The unused hardware will be cleaned up. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>AppServicePlanDeleteFailed</strong></td><td>An unused App Service Plan could not be deleted during cleanup.</td><td>This error occurs when the system fails to remove unused infrastructure as part of cleanup. The operation will be retried automatically. If the problem persists, please reach out to support.</td></tr></tbody></table>

### Environment Creation and Deletion Errors

<table><thead><tr><th width="261">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>AddEnvironmentFailedInitialize</strong></td><td>We encountered an issue while setting up your environment.</td><td>This error occurs when there is an issue during the setup process of a new environment. Verify configurations, permissions, or connectivity and retry the environment setup.</td></tr><tr><td><strong>AddEnvironmentFailedDatabase</strong></td><td>There was a problem creating the database during environment creation.</td><td>This error occurs when creating the database during environment setup fails. Verify database settings, permissions, or connectivity and retry the environment setup.</td></tr><tr><td><strong>AddEnvironmentFailedAppService</strong></td><td>There was an error with the App Service during environment creation.</td><td>This error occurs when there is an issue with the App Service component during environment creation. Verify App Service settings, permissions, or connectivity and retry the environment setup.</td></tr><tr><td><strong>AddEnvironmentFailedStorage</strong></td><td>We ran into a storage issue while creating your environment.</td><td>This error occurs when encountering storage issues during environment creation. Verify storage resources, permissions, or connectivity and retry the environment setup.</td></tr><tr><td><strong>AddEnvironmentFailedIdentityApplication</strong></td><td>There was an error with the identity application during environment creation.</td><td>This error occurs when encountering issues with the identity application (e.g., authentication or authorization service) during environment creation. Verify identity application settings, permissions, or connectivity and retry the environment setup.</td></tr><tr><td><strong>AddEnvironmentFailedUnknown</strong></td><td>An unknown error occurred while adding your environment.</td><td>This error indicates an unexpected issue occurred during the addition of a new environment. Contact support for assistance in diagnosing and resolving the issue.</td></tr><tr><td><strong>DeleteEnvironmentFailedNotFound</strong></td><td>Used when the environment requested to be deleted could not be found in Hosting Management.</td><td>This error occurs when attempting to delete an environment that cannot be located in the hosting management system. Verify environment identifiers and permissions and retry the deletion operation.</td></tr><tr><td><strong>MoveEnvironmentFailed</strong></td><td>The environment could not be moved to its new hosting.</td><td>This error occurs when the system encounters an issue while moving an environment between App Service Plans or tiers. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>ConfigureMovedEnvironmentFailed</strong></td><td>The environment was moved successfully but could not be reconfigured.</td><td>This error occurs after a successful environment move when the system is unable to reconfigure the environment's relations to other environments. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>MoveWithinSameTierNoTargetOrEviction</strong></td><td>An environment move within the same plan could not be completed because no target was specified.</td><td>This error occurs when a move within the same hosting plan is requested but the system cannot determine where to place the environment. Please reach out to support for assistance.</td></tr><tr><td><strong>MoveEnvironmentDedicatedTargetNotFound</strong></td><td>The dedicated hosting target could not be located for the environment.</td><td>This error occurs when the system has provisioned all required dedicated infrastructure but cannot identify where to place a specific environment. Retry the operation, and if the problem persists, please reach out to support.</td></tr><tr><td><strong>DatabaseDeleteActionNotSupported</strong></td><td>Deleting databases as part of an environment change is not supported.</td><td>This error occurs when a change attempts to delete a database, which is not currently supported. Please reach out to support for assistance.</td></tr></tbody></table>

### Deployment Update and SiteExtension Errors

<table><thead><tr><th width="262">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>DeploymentUpdateUnableToInitializeUpdateInSiteExtension</strong></td><td>Some preflight checks failed from the Deployment Update service.</td><td>This error occurs when preflight checks from the Deployment update service fail, preventing the initialization of the update process. Retry the operation after verifying configurations and permissions.</td></tr><tr><td><strong>DeploymentUpdateSourceSiteExtensionNotFound</strong></td><td>We were unable to reach the source SiteExtension - either 404 or BadRequest.</td><td>This error occurs when the system cannot locate or access the source SiteExtension required for the deployment update process. Verify source SiteExtension settings and retry the deployment update.</td></tr><tr><td><strong>DeploymentUpdateTargetSiteExtensionNotFound</strong></td><td>We were unable to reach the target SiteExtension - either 404 or BadRequest.</td><td>This error occurs when the system cannot locate or access the target SiteExtension required for the deployment update process. Verify target SiteExtension settings and retry the deployment update.</td></tr><tr><td><strong>DeploymentUpdateDeploymentTimedOut</strong></td><td>We never got a completed or failed answer from the SiteExtension within our timeout.</td><td>This error occurs when the deployment update process does not receive a response (completed or failed) from the SiteExtension within the expected time frame. Adjust timeout settings and retry the deployment update.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionCantConnectToRemoteRepository</strong></td><td>SiteExtension preflight, can't reach the remote repository.</td><td>This error occurs when the SiteExtension encounters difficulties connecting to the remote repository during preflight checks. Verify network settings, repository permissions, or firewall configurations and retry the operation.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionIsSourceBusy</strong></td><td>SiteExtension preflight, the source is busy.</td><td>This error occurs when the SiteExtension detects that the source environment or repository is currently busy and unavailable for updates. Retry the operation later when the source environment is less busy.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionIsTargetBusy</strong></td><td>SiteExtension preflight, the target is busy.</td><td>This error occurs when the SiteExtension detects that the target environment or repository is currently busy and unavailable for updates. Retry the operation later when the target environment is less busy.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionIsConfiguredForUmbracoDeploy</strong></td><td>SiteExtension preflight, UmbracoDeploy API key not found or configured.</td><td>This error occurs during preflight checks when the SiteExtension is not properly configured with the necessary UmbracoDeploy API key. Verify and configure the API key correctly in the SiteExtension settings to resolve the issue.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionGitPullFailed</strong></td><td>Unable to do a Git pull, if it was required.</td><td>This error occurs when the SiteExtension fails to perform a Git pull operation as part of the deployment update process. Verify repository settings, permissions, or authentication and retry the operation.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionGitPushFailed</strong></td><td>This also hides a build error - it's the Kudu process that kicks in, so it's a combined Git push + Kudu deploy.</td><td>This error occurs when the Git push and subsequent Kudu deployment process fails during the deployment update. Review Kudu logs for detailed error messages and retry the operation.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionExtractionFailed</strong></td><td>Umbraco Deploy tried to extract changes but encountered a problem. Please review the CMS log files for detailed information.</td><td>This error occurs when Umbraco Deploy encounters difficulties while extracting changes during deployment updates. Review CMS log files for detailed error messages and take corrective actions as necessary.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionUnableToGetDeployExtractionStatus</strong></td><td>Unable to get the status of Umbraco Deploy extraction.</td><td>While polling for the status of a running Umbraco Deploy extraction, the request to the target environment failed. The extraction may have been interrupted or the target became unreachable. Check the status of the extraction in the backoffice of the target environment. Go to the Settings section and open the Deploy dashboard.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionExtractionTimedOut</strong></td><td>Umbraco Deploy extraction timed out.</td><td>This error occurs when the Umbraco Deploy extraction process exceeds the expected time limit during the deployment update. Adjust timeout settings and retry the deployment update.</td></tr><tr><td><strong>DeploymentUpdateSiteExtensionTargetUnavailable</strong></td><td>The SiteExtension went down and was unable start up again.</td><td>This error occurs when the SiteExtension shuts itself down on the target environment and is unable start up again. Restart the target environment and retry the deployment.</td></tr></tbody></table>

### Database Allocation and Movement Errors

<table><thead><tr><th width="268">Error name</th><th>Description</th><th>Extended Explanation</th></tr></thead><tbody><tr><td><strong>UnableToAllocateDatabaseSlotTimeoutExceeded</strong></td><td>Unable to allocate a database slot within the time limit.</td><td>This error occurs when the system fails to allocate a database slot within the designated time frame. The issue could be due to resource constraints, network latency, or high system load. Retry the operation after some time or check for any underlying resource limitations or connectivity issues. If the problem persists, consider reaching out to support for further assistance.</td></tr><tr><td><strong>UnableToMoveDatabaseToAnotherResourceUnit</strong></td><td>An unexpected error occurred while trying to move the resource unit. Please retry the operation or reach out to support.</td><td>This error indicates that an unexpected issue was encountered while attempting to move the database to another resource unit. This can be caused by conflicts in resource allocation, network issues, or internal errors. Retry the operation after some time, and if the issue persists, contact support for detailed diagnostics and resolution steps.</td></tr><tr><td><strong>UnableToMoveDatabaseServer</strong></td><td>We were unable to move the database to a new database server. The operation either timed out or failed. Please retry the operation again or reach out to support.</td><td>This error occurs when the system fails to move the database to a new server, either due to a timeout or an operational failure. This could be caused by connectivity issues, resource limitations, or server misconfigurations. Retry the operation after verifying the server settings and ensuring adequate resources. If the problem continues, contact support for further assistance and troubleshooting.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/cloud-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.