# Zuul cannot upload a collection release saying that it already exists but it doesn't

**URL:** <https://forum.ansible.com/t/zuul-cannot-upload-a-collection-release-saying-that-it-already-exists-but-it-doesnt/1898>\
**Category:** Get Help\
**Tags:** bug, galaxy-ng\
**Created:** [October 24, 2023, 9:02am UTC](https://forum.ansible.com/t/zuul-cannot-upload-a-collection-release-saying-that-it-already-exists-but-it-doesnt/1898 "2023-10-24T09:02:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [October 25, 2023, 7:46am UTC](https://forum.ansible.com/t/zuul-cannot-upload-a-collection-release-saying-that-it-already-exists-but-it-doesnt/1898/4 "2023-10-25T07:46:07Z")

</div>

@tannerjc ok, how can i now upload the collection? I can’t do it manually because of the [error](http://forum.ansible.com/t/fails-to-upload-a-collection-new-version-tarball-with-no-permission-but-im-a-namespace-owner/1899) and with Zuul. Could anybody remove the artifact?  
I guess it’d be faster for me to try to release a mock 5.0.2 release but it would be wrong.

---

_[View the full topic](https://forum.ansible.com/t/zuul-cannot-upload-a-collection-release-saying-that-it-already-exists-but-it-doesnt/1898)._