Skip to main content

Application deletion

Without restrictions, deleting an application is a one-click way to break production. SimplAI prevents two kinds of accidental deletion:

  1. Deleting an application that is currently deployed.
  2. Deleting an application that is used by other applications (a dependency).

Draft applications without these conditions can be deleted freely — there's nothing to break.

Deployed applications​

If the application is currently deployed (live to users via API, embed, telephony, or any other deployment surface), you must first disable the application before deleting it.

Attempting to delete a deployed app shows:

This application is currently deployed. Please disable it before deletion.

The flow is: open the application → disable it (turns off the deployment surface) → return to the list → delete.

This protects against the case where someone deletes an application that's still serving live user traffic.

Applications used by other applications​

If the application is published and used by other applications (e.g., a Tool referenced by an Agent, an Agent invoked as a sub-agent by another Agent), you must first remove it from every dependent application before deletion.

Attempting to delete shows an error message listing the dependents with deep-links to each one:

This application is currently in use by other applications. Please remove it from the following before deletion:

  • [Application Name 1 — link]
  • [Application Name 2 — link]

The check considers both the current draft state and the published state of the dependent applications.

Model and connection usage​

Beyond app-to-app dependencies, deletion also surfaces resource usage so you don't break models or connections downstream:

  • For an Agent — if a model is being used by the agent in its published or current state, you're told which model and where.
  • For a Tool — if a model is in use, you're told how many places (LLM model usage count) the model is used by the application.
  • For Connections — when deleting an application that has a Connection, you're told which Tools currently use that Connection.

These warnings don't block deletion of the application itself, but they make the impact obvious before you commit.

Draft applications​

Draft applications that are not deployed and have no dependents can be deleted without restrictions. The standard delete-confirmation dialog is shown.

Audit logging​

Every successful deletion — and every blocked deletion attempt — appears in the Audit log with the resource type, the actor, and the action.