Why were my resources not destroyed when I undeployed a configuration?

You tried to undeploy a configuration, but it failed.

The project displays a Needs attention alert and a message displays on the Activity tab that states that the configuration failed to undeploy.

Go to the needs attention widget on the Overview tab and select Failed to undeploy to view the Schematics logs, which provide more information about the failure.

• Permissions for the API Key or trusted profile were changed: For more information about the required access for trusted profiles, see Using trusted profiles to authorize projects.
• A service was down when you tried to undeploy a configuration: Check the Status page for the service, and try to undeploy the configuration again when the service is back up.
• The deployable architecture that your configuration is based on contains bugs that caused a failure when you tried to undeploy it.
• Though not recommended, some resources might need to be destroyed one by one in the Schematics resource list. For more information, see Undeploying resources created by projects.