# What should I do with incomplete multipart uploads?

Canonical URL: https://help.iagenify.com/faqs/object-storage/what-should-i-do-with-incomplete-multipart-uploads

[← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)

HELP CENTER · FAQ Object Storage 1 min read
# What should I do with incomplete multipart uploads?
Multipart upload lets a large object be sent in parts, but an interrupted workflow can leave uploaded parts that are not yet a complete object. These parts may continue to consume storage until the upload is completed or explicitly aborted, depending on the service’s behavior.
IaGenify
Object Storage

## Find and classify unfinished uploads
Use the provider’s listing or lifecycle controls to identify uploads that have remained incomplete beyond the expected transfer window. Check whether an active client is still sending parts before cleanup, especially for long-running transfers.
Associate upload identifiers with the intended object and initiating job where possible. This helps distinguish abandoned attempts from a slow but valid upload and gives support teams a traceable reason for cleanup.
## Clean up without removing valid data
Abort only the incomplete upload identifier after confirming the transfer is abandoned; do not delete the completed object at the same key. Where supported, configure a lifecycle rule for stale incomplete uploads and test its scope first.
Monitor incomplete upload counts and cleanup results. Document how clients resume or restart transfers, since retry behavior may differ by SDK, provider, and upload design. [← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)