Sometimes, during migration (or any other massive upload process), it's possible to accidentally issue multiple re-uploads requests for the same image due to a bug in the code.
Cloudinary Uploader's default behaviour is to allow overwriting of any existing resource in the case of a names collision. Therefore such re-uploads will succeed and result in an increased consumption of Monthly Transformations.
It's strongly advised to have good monitoring on your uploads and to be alerted to such exaggerated activity. This will allow you to take actions and prevent unnecessary plan upgrades and additional costs.
Our plan to change every image reference in our application was slowed by the holidays. We have over 6 million lines of code and it's been very hard to make this radical of a change. Is it possible to get three more weeks deferral?
Or can a fix be made that a 404 does not create a resource at Cloudinary?
Below is a link to a new and extended article on this subject:
For personal billing issues please contact our customer-success team and we'll be happy to assist.
Please sign in to leave a comment.