Project delete
- Only an archived project can be deleted, by its Owner or a system admin.
- You type the project name to confirm. Members lose access at once.
- The project waits before it is purged. Admins set the Project delete delay in Feature Administration > Time limits (default 7 days; see Admin settings). You can choose a longer delay for the project, up to 30 days, never shorter than the project delete delay.
- Until the purge runs, an Owner or admin can Restore it (the card banner, or Cancel Delete in the card menu). Members get their access back.
- The purge runs hourly. It waits while the project still has running sessions or jobs.
- You choose which managed storage to delete with it. Attached and external storage is never deleted.
- A checked managed bucket that still has files is not deleted. It stays, listed for admins as orphaned, with any storage you did not check.
- Job and cost history is kept.
- A failed job does not block delete after it is cleared. Stop running and clear failed (N) in the delete dialog stops running and starting sessions and flows, then cleans up failed jobs and marks them done.
eureka project clear-failed NAMEclears failed jobs and leaves running work alone. See Archive, restore, or delete a project.