Understand the quota boundary
Each IaGenify Cloud storage has its own capacity limit; object storage does not share one pooled allowance with the account's databases. A file that would push the object storage beyond its current quota is rejected rather than partly stored. The exact available space depends on the account's plan and any active add-on, so check the account's current usage instead of relying on an old figure.
A quota error is different from an invalid key or an access problem. If the request names a valid object and the storage is available, inspect the used and allowed space for that specific storage. A failed write should not be treated as a completed upload; check the result before passing the object key to another step.
Free space without losing required objects
List the objects or prefixes used by the application and identify data that can be safely removed. Confirm retention requirements and downstream references before deleting an object, since workflows or users may still depend on its key. Removing a saved storage connection is not the way to free space if you need its contents.
After deleting unneeded objects or arranging additional capacity, retry the upload and verify its returned key and size. Keep large generated files, temporary exports, and long-term records organized so you can make informed cleanup decisions. If the reported usage does not match what you can list, capture the storage identifier, usage response, and sanitized error for support.