# Renaming large files causing possible Fusion error

**URL:** <https://community.seqera.io/t/renaming-large-files-causing-possible-fusion-error/918>\
**Category:** Ask for help\
**Tags:** nextflow, fusion, aws\
**Created:** [July 3, 2024, 9:44pm UTC](https://community.seqera.io/t/renaming-large-files-causing-possible-fusion-error/918 "2024-07-03T21:44:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Julien\_Fouret](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/julien_fouret/32/572_2.png) [@Julien\_Fouret](https://community.seqera.io/u/Julien_Fouret)\
**Post date:** [July 12, 2024, 3:29pm UTC](https://community.seqera.io/t/renaming-large-files-causing-possible-fusion-error/918/5 "2024-07-12T15:29:05Z")

</div>

Hi,

I have the same issue using the pipeline nf-core/cellranger v 2.7 while making a custom reference with cellranger aligner.

I seems that the star index is moved at the end by the cellranger executable and I have this same error in an AWSBATCH environment using fusion/wave.

Thx,

---

_[View the full topic](https://community.seqera.io/t/renaming-large-files-causing-possible-fusion-error/918)._