Deployment deletion shows "resource is associated with deployments currently being deleted"

Last updated: August 25, 2026

Symptom

After deleting a LangGraph Platform (cloud) deployment, you try to delete the associated tracing project and get an error like:

resource is associated with deployments currently being deleted

This can show up immediately after the deployment delete request, and the project stays locked even though the deployment itself appears gone.

Cause

Deployment deletion runs as an asynchronous two-phase teardown. The deployment is marked for deletion and removed from view right away, but the underlying resources, including the linked tracing project, are cleaned up in a background process afterward. Until that background cleanup finishes, the tracing project stays locked and returns the "currently being deleted" error if you try to delete it directly.

This is expected behavior, not a stuck or failed deletion.

Resolution

No action is needed. The lock clears on its own once the background teardown finishes, typically within about a week of the original delete request.

Retrying the delete with API flags such as force=true or delete_tracing_project=true will not speed this up: the tracing project is locked by the pending teardown, not by a missing flag on the delete call. If the tracing project is still locked well past that window, that's worth flagging as unusual, but the normal case resolves without intervention.

References