---
title: "Retry a Droplet Destroy with Associated Resources Request"
method: POST
path: "/v2/droplets/{droplet_id}/destroy_with_associated_resources/retry"
tags: ["DigitalOcean-public.v2-new_Droplets"]
---

# Retry a Droplet Destroy with Associated Resources Request

`POST /v2/droplets/{droplet_id}/destroy_with_associated_resources/retry`

If the status of a request to destroy a Droplet with its associated resources
reported any errors, it can be retried by sending a POST request to the
`/v2/droplets/$DROPLET_ID/destroy_with_associated_resources/retry` endpoint.

Only one destroy can be active at a time per Droplet. If a retry is issued
while another destroy is in progress for the Droplet a 409 status code will
be returned. A successful response will include a 202 response code and no
content.

## Path parameters

- `droplet_id` integer, required

## Response `202`

This does not indicate the success or failure of any operation, just that the request has been accepted for processing.

## Other responses

- `401` — Authentication failed due to invalid credentials.
- `404` — The resource was not found.
- `409` — The request could not be completed due to a conflict.
- `429` — The API rate limit has been exceeded.
- `500` — There was a server error.
- `default` — There was an unexpected error.

---

[API](https://skmtc.net/digitalocean/apis/digitalocean-api.md) · [All operations](https://skmtc.net/digitalocean/apis/digitalocean-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/digitalocean/digitalocean-api/revisions/cb3bf9b21459/schema)