Skip to main content
Deleting a project from DryRunPro is a teardown of the DryRunPro overlay for that Adobe Commerce Cloud project. It does not delete the Adobe Commerce Cloud project on the Adobe side. The live storefront, the Adobe-side environment list, the Adobe user roster, and the Magento codebase are untouched. This page documents what the Delete Project button actually does, what is destroyed, what is preserved, the irreversible warning, and how to add a project back if you delete it by mistake.

​
When you would delete a project

Common reasons to delete:
  1. Customer offboarding. A merchant has left your agency. You no longer manage their Adobe Commerce Cloud project, and you do not want their card on your DryRunPro Projects tab.
  2. Tenancy split. Your business has split into two tenancies (for example, two regions or two trading entities) and you are moving a project to a different DryRunPro tenancy.
  3. Mistaken add. You added the wrong Cloud Project ID during the Add Project wizard and want to start over.
  4. Customer migration off Adobe Commerce Cloud. The merchant is decommissioning their Adobe Commerce Cloud project (moving to a different platform). Once the Adobe-side project is gone, the DryRunPro card has nothing to operate on, and you can delete it.
If you are simply pausing operations on a project (no dryruns for a while), you do not need to delete. Inactive cards do not consume resources. Leave them alone.

​
Where the Delete Project button is

There are two places:
  • On the project card on the Projects tab, the red Delete Project button at the bottom-left of every card.
  • On the Project Overview page, a red Delete Project button directly under the project name in the header.
Both buttons trigger the same workflow.

​
The Delete Project workflow

When you click Delete Project, DryRunPro does not delete immediately. It opens a confirmation dialog with three explicit consequences listed:
  1. The DryRunPro project card will be removed.
  2. Any running dryrun environments for this project will be terminated.
  3. Any Docker packages and snapshots produced from past dryruns will become inaccessible.
You must type the project name into a confirmation field (or in some legacy tenancies, tick “I understand this is irreversible”) and click the red Delete button to commit. Cancelling the dialog leaves everything intact.

​
What is destroyed

When the deletion completes, the following DryRunPro-side state is destroyed:
  • The project card on the Projects tab.
  • Every running dryrun environment for the project, regardless of state. The container fleet is terminated, the public URL is revoked, the Fastly entry is removed.
  • All Docker snapshots and Warden packages produced by past dryruns for this project. The download links on the Docker packages tab disappear.
  • All snapshot artefacts (codebase, media, database snapshots) from the Project Overview, Snapshots tab.
  • The DryRunPro Project ID (the thirteen-character handle). It is permanently retired and not reused.
  • The encrypted Cloud API token stored in Project credentials.
  • Any DRP Composer overrides saved on the project.
  • The team assignment is dropped (the team itself is not deleted, only the link from this project to the team).
  • Audit logs for the project remain available in the platform-level audit log for 90 days, then are purged on schedule.

​
What is preserved

The following is not destroyed by Delete Project:
  • The Adobe Commerce Cloud project itself. The live storefront, the Adobe-side environments, and the Magento codebase are untouched. To delete the Adobe-side project you need to do that on the Adobe side using Cloud Manager or your Adobe account manager.
  • The Adobe-side Users roster. Engineers who had access to the Cloud project still have it.
  • The deploy-bot user (e.g. docker@247commerce.co.uk) remains as a super-admin on the Adobe-side project. If you intend to also remove the deploy bot, do that separately on the Adobe side.
  • DryRunPro user accounts. Users who were invited to DryRunPro for this project are not deleted. They keep their DryRunPro account and continue to have access to other projects in the tenancy.
  • Teams. Teams that were assigned to this project remain. Only the assignment link is broken.

​
Irreversible warning

DryRunPro phrases the deletion as irreversible because the DryRunPro Project ID, the Docker snapshot library, and the dryrun URLs cannot be recovered. If you re-add the same Cloud Project ID after deletion, the new project gets a new DryRunPro Project ID, fresh Docker snapshot library, and a fresh URL pool. Any links you had shared (e.g. https://staging-47k74xtjq6jya-2.dryrunpro.com) will not resolve. The Adobe Commerce Cloud project itself is, of course, recoverable; it is the same project, you just disconnected it from DryRunPro.

​
Re-adding a deleted project

If you delete a project by mistake:
  1. Go to the Add Adobe Commerce Cloud Project wizard.
  2. Confirm the deploy bot is still super-admin on the Adobe side. If you only deleted the DryRunPro overlay, the deploy bot is still in place and you can skip steps 1 to 4.
  3. Paste the same Cloud Project ID and click Check access & Save.
The card reappears, but with the caveats listed above (new Project ID, no historical dryruns, no historical snapshots).

​
Pre-conditions

Before you delete, confirm:
  1. No engineers are mid-flight on a dryrun for this project. Check Dryrun Environments for active environments. Deleting will kill them.
  2. Any artefacts you might want to keep (Docker snapshots, Warden packages, codebase snapshots) have been downloaded. After deletion the download links are gone.
  3. The customer has been informed, if this is a customer-facing project. Their team will lose visibility.
  4. You have the right to delete. Only an Admin role with the adobe_commerce_delete permission can delete a project. See Roles and Permissions.

​
What appears in audit logs

The deletion is recorded in the platform-level audit log with:
  • The deleting user’s email and ID.
  • Timestamp.
  • The DryRunPro Project ID being deleted.
  • The Adobe Cloud Project ID it was bound to.
  • The team assignment at time of deletion.
  • A list of dryrun environments terminated by the action.
The audit entry survives the deletion. Even though the project is gone, the log entry remains for 90 days and supports compliance review.

​
Frequently asked questions

Will deleting the project delete the Adobe Commerce Cloud project on the Adobe side? No. DryRunPro does not have, and does not need, the rights to delete the Adobe-side project. Only the DryRunPro overlay is destroyed. Will my customer lose access to their Magento Cloud storefront? No. The customer’s storefront is on the Adobe side. DryRunPro is just a staging overlay. Removing the overlay has no effect on the live storefront. Are Docker snapshots backed up anywhere before deletion? No. They are produced and held in the DryRunPro tenancy storage layer. If you need to keep them, download them from the Docker packages tab before clicking Delete Project. Can I delete a project that has running dryruns? Yes, but the running dryruns will be terminated as part of the deletion. The confirmation dialog calls this out explicitly. What happens to users who were invited to DryRunPro for the project? The user accounts remain. Their access to this specific project is removed. If they have access to other projects (via teams or direct assignment), they keep that access. The button is greyed out for me. You do not have the adobe_commerce_delete permission. Only Admin roles can delete projects. Ask your DryRunPro tenancy admin to delete on your behalf. I deleted by mistake. Can support restore the DryRunPro Project ID? The Project ID itself is not restorable; once retired it stays retired. Support can re-establish the connection with a new ID, but historical artefacts (Docker snapshots, dryrun URLs) cannot be restored. Does deleting affect the team that was assigned? No. The team itself is preserved. Only the link from this project to the team is broken.