This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

Destroy returning "not found"

Comments

4 comments

  • Avatar
    Danny Valentine

    Hi Hamzat.

    My name's Danny, and I'm one of the Developer Support engineers here on Cloudinary's Customer Success team. I've had a look at our logs and see a number of successful destroy requests. Could you please provide me with the public_id of an asset that claims not to be found, as well as the full JSON response that is returned?

    If you're conscious of posting these details publicly, you're welcome to submit a support ticket privately instead.

    Looking forward to hearing back from you!
    -Danny

    0
    Comment actions Permalink
  • Avatar
    Hamzat Azeez

    Hello Danny, thank you very much for your response. The public_id of the asset is zrcrhjndn7s74uogd0to and the full JSON response that is returned is 

    { result: 'not found' }
    0
    Comment actions Permalink
  • Avatar
    Hamzat Azeez

    I have been able to get it working. I needed to supply the right 'resource_type' parameter in the delete request. Thanks.

    0
    Comment actions Permalink
  • Avatar
    Michal Kuperman

    Hi Hamzat,

    Thanks for providing the public_id. 

    When using the destroy method via the SDK, by default we look for an image reousrce_type, since this resource is a video, you would need to include "resource_type" set to "video" in the request as explained here: https://cloudinary.com/documentation/image_upload_api_reference#destroy_optional_parameters

    For now, I see that you managed to destroy this video. 
    Please let us know if you need any further assistance.

    Thanks,
    Michal

    0
    Comment actions Permalink

Post is closed for comments.